dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-12882

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Clasifico Listing plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 2.0. This is due to the plugin allowing users who are registering new accounts to set their own role by supplying the 'listing_user_role' parameter. This makes it possible for unauthenticated attackers to gain elevated privileges by registering 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 confidence

The Clasifico Listing WordPress plugin versions up to 2.0 contains a privilege escalation vulnerability where the user registration function accepts a 'listing_user_role' parameter, allowing unauthenticated attackers to specify an administrator role during account creation and gain full site control.

MitigationImmediately remove or sanitize the 'listing_user_role' parameter in the registration logic to prevent user-supplied role assignment, audit existing user accounts for unauthorized administrators, and update to a patched version when released.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Clasifico Listing plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Clasifico Listing'. Note the installed version number.
    Affected if Plugin is installed and version is 2.0 or lower (no patch version specified)
  2. Confirm user registration is enabled
    In WordPress admin, go to Settings > General and verify 'Membership: Anyone can register' is checked, and a default role is selected.
    Affected if User registration is enabled and the plugin's registration form is accessible to unauthenticated users
  3. Inspect registration function for role parameter
    Access the plugin source code (wp-content/plugins/clasifico-listing) and examine the user registration handler. Search for 'listing_user_role' or similar user-supplied role assignment logic.
    Affected if The registration code accepts and applies a role parameter from user input without validation
  4. Check for unauthorized administrator accounts
    In WordPress admin, go to Users > All Users and review all accounts with Administrator role. Note creation dates and email addresses unfamiliar to your organization.
    Affected if There are administrator accounts you did not create, especially with recent creation dates or suspicious email addresses

You are affected if the Clasifico Listing plugin version 2.0 or lower is installed, user registration is enabled, and the plugin accepts a user-supplied role parameter in the registration flow.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately remove or sanitize the 'listing_user_role' parameter in the registration logic to prevent user-supplied role assignment, audit existing user accounts for unauthorized administrators, and update to a patched version when released.

Recommended fix Moderate confidence

Latest version after 2.0 (confirm via WordPress plugin repository or vendor)

  1. 1. Check the current version of the Clasifico Listing plugin installed on your WordPress site
  2. 2. If the installed version is 2.0 or earlier, update to the latest available version of the plugin
  3. 3. After updating, verify that the plugin settings no longer allow user-supplied role assignment
  4. 4. Review existing user accounts to ensure no unauthorized administrator accounts were created
  5. 5. Consider resetting passwords for all administrator-level accounts as a precaution

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12882 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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