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

> Authenticated users with post-editing privileges can modify or delete WPCode Library authentication keys due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2023
- **Updated:** 6 Mar 2025
- **Also known as:** GHSA-fc29-rq2p-4h73

## What is CVE-2023-0328?

CVE-2023-0328 is a medium-severity missing authorization vulnerability in Unknown WPCode, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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).

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-0328?

It affects 1 product.


Products: Wpcode Wpcode.

## How do I fix CVE-2023-0328?

No fix has been published for CVE-2023-0328 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-0328 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0328 exists.

## Other vulnerabilities in Unknown WPCode

- [CVE-2023-1624](https://insights.sbomify.com/CVE-2023-1624/): WPCode Lite < 2.0.9 - Arbitrary Log File Deletion via CSRF (medium 6.5)
- [CVE-2023-3524](https://insights.sbomify.com/CVE-2023-3524/): WPCode < 2.0.13.1 - Reflected XSS (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0328 and fix it if it is affected.

What it is: CVE-2023-0328 is a medium-severity missing authorization vulnerability in Unknown WPCode, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0328 exists.

Affected product: Unknown WPCode. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-0328/ (Markdown: https://insights.sbomify.com/CVE-2023-0328/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-0328
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-0328
- OSV: https://osv.dev/vulnerability/CVE-2023-0328

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-0328/
Summaries are generated and may contain mistakes; the official description above is the record.