dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-42640

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Unauthenticated Broken Access Control in Classified Listing <= 5.3.8 versions.

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 · moderate confidence

Unauthenticated Broken Access Control vulnerability in the Classified Listing plugin for WordPress allows unauthenticated users to access resources or perform actions that should require proper authorization. The vulnerability exists in versions 5.3.8 and below, indicating a failure to enforce access control checks on certain endpoints or functionalities within the plugin.

MitigationUpgrade Classified Listing plugin to a version newer than 5.3.8. If a patch is unavailable, restrict access to vulnerable endpoints via web server configuration or implement additional access control checks at the application level.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Classified Listing' (by RadiusTheme). Alternatively, check the plugin files in /wp-content/plugins/classified-listing/ directory for version information in the main plugin file or readme.txt
    Affected if Classified Listing plugin is not installed - not affected
  2. Determine installed plugin version
    Check the plugin version in the plugin header of /wp-content/plugins/classified-listing/classified-listing.php, or view the plugin details in WordPress admin Plugins page
    Affected if Version is 5.3.8 or lower - potentially affected
  3. Check for exposed REST API or AJAX endpoints
    Examine the plugin directory for exposed endpoints: look in /wp-content/plugins/classified-listing/ for REST API route definitions (typically in includes/Api or similar folders) and AJAX action handlers. Use a tool like WPScan or manual enumeration to identify publicly accessible endpoints related to listings, user data, or admin functions
    Affected if Unauthenticated access to sensitive listing/user management endpoints is possible - likely affected by this CVE
  4. Test for unauthorized access to listing functionalities
    Using a tool like Burp Suite or curl, attempt to access common listing endpoints (such as wp-json/classified-listing/v1/* or admin-ajax.php?action=rtcl*) without authentication. Check if responses return data or perform actions that should require login
    Affected if Requests return sensitive data or complete actions without authentication tokens - vulnerable to this broken access control issue

If the Classified Listing plugin version is 5.3.8 or below and unauthenticated users can access or modify listing data without login credentials, the environment is affected by CVE-2026-42640.

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

Upgrade Classified Listing plugin to a version newer than 5.3.8. If a patch is unavailable, restrict access to vulnerable endpoints via web server configuration or implement additional access control checks at the application level.

Recommended fix Moderate confidence

Classified Listing > 5.3.8 (latest version, ideally 5.3.9 or higher)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find "Classified Listing" plugin
  4. Check the current version is below 5.3.9
  5. If vulnerable, click "Update Now" to upgrade to the latest version, or manually download the latest version from WordPress.org and upload via Plugins > Add New > Upload Plugin

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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