dbcve.org
Classified ListingWordPress extension · Radiustheme

CVE-2024-1352

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 3.0.5 or later.
See remediation →
62/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
The Classified Listing – Classified ads & Business Directory Plugin plugin for WordPress is vulnerable to unauthorized access & modification of data due to a missing capability check on the rtcl_import_location() rtcl_import_category() functions in all versions up to, and including, 3.0.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to create terms.

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 versions up to 3.0.4 lack proper capability checks on the rtcl_import_location() and rtcl_import_category() functions, allowing any authenticated user with subscriber-level access to create taxonomy terms (locations and categories) without authorization.

MitigationUpdate the plugin to version 3.0.5 or later which includes proper capability checks, or manually add capability verification (e.g., current_user_can('manage_options')) to both functions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check the installed version of the Classified Listing plugin
    In WordPress admin, go to Plugins > Installed Plugins, find 'Radiustheme Classified Listing' and note the version number displayed
    Affected if The version shown is less than 3.0.5 (for example, 3.0.4, 3.0.3, etc.)
  2. Verify the vulnerable functions exist in the plugin
    Access the WordPress site files via FTP or file manager, navigate to /wp-content/plugins/classified-listing/, search for the functions rtcl_import_location() and rtcl_import_category() in the PHP files
    Affected if Both functions are found in the plugin code without any capability check (such as current_user_can()) at the beginning of each function
  3. Confirm if the site has user accounts with subscriber-level access
    In WordPress admin, go to Users and review the role assigned to each user account
    Affected if There is at least one user with the 'Subscriber' role (or any role below Editor/Author) active on the site
  4. Check if the REST API endpoints for the vulnerable functions are accessible
    Test accessing the endpoint that calls rtcl_import_location or rtcl_import_category while logged in as a subscriber-level user (the exact endpoint path depends on the plugin implementation, but typically it would be /wp-json/classified-listing/v1/import/location or similar)
    Affected if The request succeeds and creates a new location or category term without returning a permission denied error

A site is affected if it runs Classified Listing plugin version below 3.0.5 AND has at least one subscriber-level user account, since such users can exploit the missing capability checks to create taxonomy terms without authorization.

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 capability checks, or manually add capability verification (e.g., current_user_can('manage_options')) to both functions.

Recommended fix High confidence

Classified Listing plugin version 3.0.5

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate the 'Classified Listing' plugin
  3. If an update is available, click 'Update Now' to update to version 3.0.5 or higher
  4. Alternatively, go to Plugins > Add New > Upload and upload the version 3.0.5 of the Classified Listing plugin
  5. After updating, verify the plugin version shows 3.0.5 or newer in the plugins list

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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