# CVE-2025-39413: WordPress Simple Sitemap – Create a Responsive HTML Sitemap plugin <= 3.6.0 - Broken Access Control vulnerability

> Attackers can bypass authorization checks in the Simple Sitemap WordPress plugin to access restricted functionality.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 30 Apr 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-mpc5-8rvq-8qfx

## What is CVE-2025-39413?

CVE-2025-39413 is a medium-severity missing authorization vulnerability in David Gwyer Simple Sitemap – Create a Responsive HTML Sitemap, published on 30 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in David Gwyer Simple Sitemap – Create a Responsive HTML Sitemap simple-sitemap.This issue affects Simple Sitemap – Create a Responsive HTML Sitemap: from n/a through <= 3.6.0.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Wpgoplugins Simple Sitemap.

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

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

## Is CVE-2025-39413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-39413 is a medium-severity missing authorization vulnerability in David Gwyer Simple Sitemap – Create a Responsive HTML Sitemap, published on 30 Apr 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-39413 in the wild and no public exploit code.

Affected product: David Gwyer Simple Sitemap – Create a Responsive HTML Sitemap. 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-39413/ (Markdown: https://insights.sbomify.com/CVE-2025-39413/index.md)
```

## Sources

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

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