# CVE-2024-12015: SQL Injection in WordPress Project Manager Plugin

> Authenticated attackers can exploit SQL injection in the Project Manager plugin to read or modify database contents.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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:** 2 Dec 2024
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-r6cg-rqqp-3rqx

## What is CVE-2024-12015?

CVE-2024-12015 is a high-severity SQL injection vulnerability in WeDevs WP Project Manager, published on 2 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The 'Project Manager' WordPress Plugin is affected by an authenticated SQL injection vulnerability in the 'orderby' parameter in the '/pm/v2/activites' route.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-12015?


## How do I fix CVE-2024-12015?

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

## Is CVE-2024-12015 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12015 and fix it if it is affected.

What it is: CVE-2024-12015 is a high-severity SQL injection vulnerability in WeDevs WP Project Manager, published on 2 Dec 2024. 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-2024-12015 exists.

Affected product: WeDevs WP Project Manager. 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-2024-12015/ (Markdown: https://insights.sbomify.com/CVE-2024-12015/index.md)
```

## Sources

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

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