CVE-2022-0836: The SEMA API WordPress plugin before 4.02 does not properly sanitise and escape some parameters before using t

Q: How do I fix CVE-2022-0836?

sema api: upgrade to 4.02. Exact commands for each OS are on this page.

Q: Is CVE-2022-0836 being exploited?

CVE-2022-0836 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-0836 affect?

CVE-2022-0836 affects sema api. Severity is critical (CVSS 9.8). The SEMA API WordPress plugin before 4.02 does not properly sanitise and escape some parameters before using them in SQL statements via an AJAX action, leading to SQL Injections exploitable by unauthenticated users

Q: How urgent is CVE-2022-0836?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2022-0836 is a critical-severity flaw (CVSS 9.8) affecting sema api. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The SEMA API WordPress plugin before 4.02 does not properly sanitise and escape some parameters before using them in SQL statements via an AJAX action, leading to SQL Injections exploitable by unauthenticated users

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 22%)
CISA exploited list	No
Weakness	CWE-89
Published	2022-05-09
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: semadatacoop

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-05-09 17:15 UTCPublished CVE record published
2026-06-17 04:21 UTCUpdated Record last modified

semadatacoop sema api UPGRADE

Affected: < 4.02

Fixed in: 4.02

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sema-api || rpm -q sema-api || sema-api --version

2. UPGRADE to 4.02 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sema-api

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sema-api

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-0836?

sema api: upgrade to 4.02. Exact commands for each OS are on this page.

Is CVE-2022-0836 being exploited?

CVE-2022-0836 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-0836 affect?

CVE-2022-0836 affects sema api. Severity is critical (CVSS 9.8). The SEMA API WordPress plugin before 4.02 does not properly sanitise and escape some parameters before using them in SQL statements via an AJAX action, leading to SQL Injections exploitable by unauthenticated users

How urgent is CVE-2022-0836?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs