# CVE-2024-13500: WP Project Manager <= 2.6.17 - Authenticated (Subscriber+) SQL Injection via orderby Parameter

> Authenticated attackers with Subscriber access can exploit SQL injection in WP Project Manager to extract sensitive database information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 15 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-ggp6-gxg7-4x89

## What is CVE-2024-13500?

CVE-2024-13500 is a medium-severity SQL injection vulnerability in wedevs Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker, published on 15 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Project Manager – Task, team, and project management plugin featuring kanban board and gantt charts plugin for WordPress is vulnerable to time-based SQL Injection via the ‘orderby’ parameter in all versions up to, and including, 2.6.17 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

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

It affects 1 product.


Products: Wedevs Wp Project Manager.

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

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

## Is CVE-2024-13500 being exploited?

There is no known exploitation of CVE-2024-13500 in the wild and no public exploit code.

## Other vulnerabilities in wedevs Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker

- [CVE-2023-3636](https://insights.sbomify.com/CVE-2023-3636/): WP Project Manager <= 2.6.4 - Arbitrary Usermeta Update to Authenticated (Subscriber+) Privilege Escalation (high 8.8)
- [CVE-2023-34383](https://insights.sbomify.com/CVE-2023-34383/): WordPress WP Project Manager Plugin <= 2.6.0 is vulnerable to SQL Injection (high 8.5)
- [CVE-2024-10174](https://insights.sbomify.com/CVE-2024-10174/): Auth bypass in Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker (high 7.3)
- [CVE-2024-13752](https://insights.sbomify.com/CVE-2024-13752/): WP Project Manager <= 2.6.17 - Missing Authorization to Authenticated (Subscriber+) Limited Arbitrary Options Update (medium 6.5)
- [CVE-2024-12195](https://insights.sbomify.com/CVE-2024-12195/): SQL injection in Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13500 is a medium-severity SQL injection vulnerability in wedevs Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker, published on 15 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13500 in the wild and no public exploit code.

Affected product: wedevs Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker. 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-13500/ (Markdown: https://insights.sbomify.com/CVE-2024-13500/index.md)
```

## Sources

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

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