# CVE-2026-74929: WP Project Manager < 4.0.7 - Subscriber+ Cross-Project Task Disclosure and Task Board Modification via IDOR

> Authenticated users can access and modify tasks in other projects due to missing authorization checks in the WP Project Manager plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-mcq5-vjfh-w694

## What is CVE-2026-74929?

CVE-2026-74929 is a medium-severity missing authorization vulnerability in Unknown Project Manager, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Project Manager  WordPress plugin before 4.0.7 does not restrict several of its REST API routes to the projects a user belongs to, allowing any authenticated user, such as a subscriber, to read other projects' task content and user email addresses and to modify other projects' task boards.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-74929?


## How do I fix CVE-2026-74929?

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

## Is CVE-2026-74929 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74929 and fix it if it is affected.

What it is: CVE-2026-74929 is a medium-severity missing authorization vulnerability in Unknown Project Manager, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74929 in the wild and no public exploit code.

Affected product: Unknown 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-2026-74929/ (Markdown: https://insights.sbomify.com/CVE-2026-74929/index.md)
```

## Sources

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

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