# CVE-2025-62965: WordPress Admin Management Xtended plugin <= 2.5.1 - Broken Access Control vulnerability

> Attackers can bypass access controls in the Admin Management Xtended WordPress plugin to perform unauthorized administrative actions.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-j46c-hfxp-3h44

## What is CVE-2025-62965?

CVE-2025-62965 is a medium-severity missing authorization vulnerability in wpseek Admin Management Xtended, published on 27 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Missing Authorization vulnerability in wpseek Admin Management Xtended  admin-management-xtended allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Admin Management Xtended : from n/a through <= 2.5.1.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-62965 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62965 is a medium-severity missing authorization vulnerability in wpseek Admin Management Xtended, published on 27 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62965 in the wild and no public exploit code.

Affected product: wpseek Admin Management Xtended. 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-62965/ (Markdown: https://insights.sbomify.com/CVE-2025-62965/index.md)
```

## Sources

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

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