CVE-2025-6994
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 Reveal Listing plugin by smartdatasoft for WordPress is vulnerable to privilege escalation in versions up to, and including, 3.3. This is due to the plugin allowing users who are registering new accounts to set their own role or by supplying 'listing_user_role' field. This makes it possible for unauthenticated attackers to gain elevated privileges by creating an account with the administrator role.
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 Reveal Listing WordPress plugin up to version 3.3 contains a privilege escalation vulnerability in its user registration functionality. The plugin accepts and applies the 'listing_user_role' parameter during account creation without proper validation, allowing unauthenticated attackers to specify 'administrator' as their role and gain full admin access to the WordPress site.
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.
-
Check Reveal Listing plugin versionIn WordPress admin, go to Plugins > Reveal Listing and note the version number displayed. Alternatively, open wp-content/plugins/reveal-listing/reveal-listing.php and locate the Version header in the plugin comments.Affected if The installed version is 3.3 or lower (versions up to and including 3.3 are affected)
-
Confirm user registration is enabledIn WordPress admin, go to Settings > General and check if the option 'Anyone can register' is enabled. Also inspect the Reveal Listing plugin settings page for any user registration functionality.Affected if User registration is enabled on the WordPress site (this is required for the vulnerability to be exploitable)
-
Audit administrator accountsIn WordPress admin, go to Users and review all accounts with the Administrator role. Note the creation date and email address for each. Look for accounts you did not create, especially those created recently or with suspicious email addresses.Affected if There are administrator accounts present that you did not create or that were created without authorization
Your environment is affected if the Reveal Listing plugin version is 3.3 or lower AND WordPress user registration is enabled, regardless of whether you detect existing exploitation.
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 version 3.4 or later if available; otherwise disable the plugin or remove the vulnerable registration functionality until a patch is released. Audit existing user accounts for unauthorized admin accounts created after the vulnerability disclosure.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6994 — 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-6994 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