SEMA API < 4.02 - Unauthenticated SQLi

published 2022-05-09 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-15882

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.8%; EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits: 0; none known

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

Patch / fix

fixed in 1

semadatacoop sema_api 4.02

Exploit prediction

1.79% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

wpscan.com https://wpscan.com/vulnerability/2a226ae8-7d9c-4f47-90af-8a399a08f03f referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

Unknown SEMA API

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

Technology feeds

WordPress rss critical rss

References

wpscan.com /vulnerability/2a226ae8-7d9c-4f47-90af-8a399a08f03f
exploit, third-party-advisory

Sources

CVE List CVE-2022-0836
NVD CVE-2022-0836

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary