dbcve.org
Classified ListingWordPress extension · Radiustheme

CVE-2024-1315

HIGH · 8.8 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 3.0.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Classified Listing – Classified ads & Business Directory Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0.4. This is due to missing or incorrect nonce validation on the 'rtcl_update_user_account' function. This makes it possible for unauthenticated attackers to change the administrator user's password and email address via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This locks the administrator out of the site and prevents them from resetting their password, while granting the attacker access to their account.

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

This is a Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Classified Listing plugin where the rtcl_update_user_account function lacks proper nonce validation. Attackers can forge administrative account changes (password and email) by tricking site administrators into clicking malicious links, enabling complete account takeover.

MitigationUpdate the plugin to version 3.0.5 or later which includes proper nonce validation. Until patched, warn administrators not to click untrusted links.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Classified ListingWordPress extension
Affected:< 3.0.5

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Classified Listing plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check for the plugin directory at /wp-content/plugins/classified-listing/
    Affected if The plugin 'Classified Listing' by Radiustheme appears in the installed plugins list
  2. Identify installed plugin version
    In WordPress admin, find Classified Listing in the plugins list and read the version number under the plugin name, or open /wp-content/plugins/classified-listing/readme.txt and look for the 'Stable tag' entry
    Affected if The version is lower than 3.0.5 (for example, 3.0.4, 3.0.3, 2.x.x, etc.)
  3. Locate the vulnerable function in plugin code
    Access the plugin files via file manager or FTP, navigate to /wp-content/plugins/classified-listing/, and search for the function named 'rtcl_update_user_account' in PHP files
    Affected if The function rtcl_update_user_account exists in the plugin code, indicating the vulnerable endpoint is present
  4. Check for nonce validation in the vulnerable function
    Open the file containing rtcl_update_user_account and examine whether wp_verify_nonce, check_ajax_referer, or check_admin_referer is called before processing the account update
    Affected if No nonce verification function is found before the account modification logic, confirming the CSRF vulnerability is present

You are affected if the Classified Listing plugin is installed with a version below 3.0.5 AND the rtcl_update_user_account function exists without proper nonce validation checks.

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
Upgrade available Upgrade to 3.0.5 or later
Fixed in 3.0.5
Interim mitigation

Update the plugin to version 3.0.5 or later which includes proper nonce validation. Until patched, warn administrators not to click untrusted links.

Recommended fix High confidence

3.0.5

  1. Back up your WordPress site database and files before making any changes
  2. Navigate to Dashboard > Plugins > Installed Plugins in WordPress admin
  3. Find the 'Classified Listing' (Classified ads & Business Directory) plugin
  4. Click 'Update now' if an update is available, or manually upload version 3.0.5
  5. Verify the plugin version shows 3.0.5 after updating
  6. Confirm administrator can log in with existing credentials
  7. Test that the rtcl_update_user_account functionality works correctly with proper nonce validation

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

Fix this in Classified Listing 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 the upgrade done

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-2024-1315 — 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-2024-1315 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