CVE-2025-14892
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Prime Listing Manager WordPress plugin through version 1.1 contains a hardcoded secret that allows unauthenticated attackers to bypass authentication and gain full administrative access to the WordPress site. This critical vulnerability enables complete site compromise without requiring any valid user account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Prime Listing Manager plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Prime Listing Manager' in the listAffected if the plugin appears in the installed plugins list
-
Check installed plugin versionClick on the plugin name in the WordPress plugins list to view its details, or inspect the plugin header in wp-content/plugins/prime-listing-manager/prime-listing-manager.php for the 'Version' fieldAffected if the version number is 1.1 or lower
-
Search for hardcoded secret in plugin filesUse a file search or grep to look for suspicious hardcoded strings in the plugin directory: grep -r 'secret\|key\|token\|password' wp-content/plugins/prime-listing-manager/Affected if any hardcoded credentials, API keys, or authentication tokens are found in the plugin code
-
Review WordPress admin user accountsIn WordPress admin, go to Users and check for any unfamiliar administrator accounts, or query the wp_usermeta table for users with wp_capabilities containing 'administrator'Affected if there are admin accounts you did not create or recognize
-
Check for recent authentication anomaliesReview WordPress access logs or security logs for requests containing unusual headers, tokens, or access from unexpected IP addresses to wp-login.php or wp-adminAffected if there are authentication attempts or admin sessions you cannot explain
You are affected if the Prime Listing Manager plugin is installed at version 1.1 or lower, or if hardcoded credentials are present in the plugin code, or if unauthorized admin accounts exist.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to the latest version if a patch is available, or remove the plugin entirely. Audit the site for unauthorized administrator accounts and reset all credentials as a precaution.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14892 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14892 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data