Classified ListingWordPress extension · Radiustheme
CVE-2023-37387
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in RadiusTheme Classified Listing plugin <= 2.4.5 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the RadiusTheme Classified Listing WordPress plugin (versions <= 2.4.5). This allows attackers to trick authenticated users into unknowingly submitting malicious requests to the plugin, potentially performing unauthorized actions such as modifying listings or changing settings.
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
<= 2.4.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin versionGo to WordPress admin > Plugins > Installed Plugins, locate 'RadiusTheme Classified Listing' and check the version number displayed. Alternatively, check the plugin's main PHP file header for the Version field.Affected if The installed version is 2.4.5 or lower.
-
Confirm plugin is activeIn WordPress admin > Plugins, verify that RadiusTheme Classified Listing shows as 'Active'.Affected if The plugin is active and running a vulnerable version.
-
Inspect forms for nonce fieldsNavigate to the plugin's front-end or admin forms (e.g., submission forms, settings pages). View the page source (right-click > View Page Source) and search for input fields containing 'nonce' or '_wpnonce'.Affected if Forms performing state-changing actions lack nonce token fields, meaning CSRF protection is missing.
-
Check AJAX actions for nonce verificationUse browser developer tools (Network tab) to capture a plugin-related AJAX request. Examine the request payload for a 'nonce' or '_wpnonce' parameter.Affected if AJAX actions that modify data do not include a valid nonce parameter.
-
Review plugin code for nonce validationAccess the plugin directory via file manager or FTP. Open PHP files that handle form submissions or settings changes. Search for 'wp_verify_nonce' or 'check_admin_referer' function calls.Affected if State-changing functions lack nonce verification calls.
If the installed plugin version is 2.4.5 or lower and the plugin lacks nonce validation on its forms or AJAX actions, the environment is vulnerable to CVE-2023-37387.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the RadiusTheme Classified Listing plugin to a version newer than 2.4.5. Additionally, implement anti-CSRF tokens (nonce validation in WordPress) on all state-changing operations and verify the Origin/Referer headers.
Fix this in Classified Listing
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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