# CVE-2024-10548: Information disclosure in Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker

> Authenticated subscribers can extract sensitive data, including hashed passwords of project owners, via the Project Task List REST API endpoint.

- **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:** 19 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-c6cm-8p8j-4fm3

## What is CVE-2024-10548?

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

### Official description

The WP Project Manager plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.6.15 via the Project Task List ('/wp-json/pm/v2/projects/1/task-lists') REST API endpoint. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive data including the hashed passwords of project owners (e.g. adminstrators).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Wedevs Wp Project Manager.

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

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

## Is CVE-2024-10548 being exploited?

There is no known exploitation of CVE-2024-10548 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-13500](https://insights.sbomify.com/CVE-2024-13500/): WP Project Manager <= 2.6.17 - Authenticated (Subscriber+) SQL Injection via orderby Parameter (medium 6.5)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10548 is a medium-severity vulnerability in wedevs Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker, published on 19 Dec 2024. 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-10548 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-10548/ (Markdown: https://insights.sbomify.com/CVE-2024-10548/index.md)
```

## Sources

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

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