# CVE-2025-3952: Missing authorization in Projectopia – Project Management Tool

> Authenticated subscribers can delete arbitrary site options, potentially causing denial of service due to missing capability checks.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **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:** 1 May 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-mgcr-297w-jg79

## What is CVE-2025-3952?

CVE-2025-3952 is a high-severity missing authorization vulnerability in Projectopia – Project Management Tool, published on 1 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Projectopia – WordPress Project Management plugin for WordPress is vulnerable to unauthorized modification of data that can lead to a denial of service due to a missing capability check on the 'pto_remove_logo' function in all versions up to, and including, 5.1.16. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary option values on the WordPress site. This can be leveraged to delete an option that would create an error on the site and deny service to legitimate users.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-3952?

It affects 1 product.


Products: Projectopia Projectopia.

## How do I fix CVE-2025-3952?

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

## Is CVE-2025-3952 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3952 and fix it if it is affected.

What it is: CVE-2025-3952 is a high-severity missing authorization vulnerability in Projectopia – Project Management Tool, published on 1 May 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-2025-3952 in the wild and no public exploit code.

Affected product: Projectopia – Project Management Tool. 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-2025-3952/ (Markdown: https://insights.sbomify.com/CVE-2025-3952/index.md)
```

## Sources

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

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