# CVE-2025-14892: Prime Listing Manager <= 1.1 - Unauthenticated Privilege Escalation

> An attacker can gain administrative access to the site without an account due to a hardcoded secret in the Prime Listing Manager plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-wj6w-x5qq-4qqw

## What is CVE-2025-14892?

CVE-2025-14892 is a critical vulnerability in Unknown Prime Listing Manager, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Prime Listing Manager WordPress plugin through 1.1 allows an attacker to gain administrative access without having any kind of account on the targeted site and perform unauthorized actions due to a hardcoded secret.

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


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

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

## Is CVE-2025-14892 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14892 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14892 is a critical vulnerability in Unknown Prime Listing Manager, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14892 exists.

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

## Sources

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

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