dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-7711

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 The Classified Listing – Classified ads & Business Directory Plugin plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 5.0.3. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.

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 Classified Listing WordPress plugin fails to validate user input before passing it to do_shortcode(), allowing authenticated users with Subscriber-level access to execute arbitrary shortcodes. This occurs because the plugin accepts a value (likely a shortcode attribute or parameter) without sanitization and directly runs it through do_shortcode(), enabling attackers to invoke any registered WordPress shortcode.

MitigationUpdate the plugin to version 5.0.4 or later once available. Until then, audit user capabilities, consider disabling public registration, and review which shortcodes are registered that could be exploited.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 Classified Listing plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Classified Listing' (author: RadiusTheme). Note the version number. Alternatively, check the plugin header in /wp-content/plugins/classified-listing/classified-listing.php
    Affected if The installed version is lower than 5.0.4 (or if version cannot be determined but the plugin is present)
  2. Confirm public user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is checked, and 'New User Default Role' is set to 'Subscriber'. This enables the attack vector of authenticated Subscriber-level access
    Affected if Public registration is enabled and the default role is Subscriber (or any role allowing shortcode injection)
  3. Identify registered shortcodes available to subscribers
    Run a WordPress debug query or check theme/plugin files for add_shortcode() calls. Common high-risk shortcodes include forms, content insertion, or third-party plugins that accept user input
    Affected if Any shortcode is registered that could be exploited to execute actions (form submission, content display, data exfiltration) when invoked via do_shortcode()
  4. Audit plugin for do_shortcode usage with user input
    Review the classified-listing plugin code for any instance of do_shortcode() that processes variables from $_GET, $_POST, or user metadata without sanitization. Search for patterns like do_shortcode($_REQUEST['...']) in the plugin files
    Affected if The plugin code contains do_shortcode() calls that process unsanitized user-supplied values

You are affected if the Classified Listing plugin version is below 5.0.4 AND public user registration is enabled allowing Subscriber-level accounts to access the vulnerable parameter/feature.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 5.0.4 or later once available. Until then, audit user capabilities, consider disabling public registration, and review which shortcodes are registered that could be exploited.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7711 — 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-7711 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