Citadela ListingWordPress extension · Ait Themes
CVE-2024-32085
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 AitThemes Citadela Listing.This issue affects Citadela Listing: from n/a before 5.20.0.
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 Citadela Listing WordPress plugin allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.
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
Citadela ListingWordPress extension
< 5.20.0CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 Citadela Listing plugin is installedCheck for the plugin directory at /wp-content/plugins/citadela-listing/ or access it via WordPress admin under Plugins > Installed PluginsAffected if The plugin directory or listing is found in the WordPress installation
-
Determine installed plugin versionOpen the main plugin file (usually index.php or citadela-listing.php) and locate the version declaration in the plugin header comment, or view the version in WordPress admin plugin listAffected if Version number is displayed and is below 5.20.0
-
Confirm plugin is activeCheck WordPress admin under Plugins > Installed Plugins to see if Citadela Listing shows as 'Active'Affected if Plugin status is Active - an inactive plugin would not be exploitable via CSRF in this context
User is affected if Citadela Listing plugin is installed, active, and the version is below 5.20.0
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.
dbcve · scoped5.20.0
Update Citadela Listing to version 5.20.0 or later. Until then, consider disabling the plugin or implementing additional request validation on the server side.
5.20.0
- 1. Back up your WordPress site and database before performing any updates.
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
- 3. Locate the Citadela Listing plugin in the list.
- 4. If an update is available, click 'Update Now' to upgrade to version 5.20.0 or later.
- 5. Verify the update completed successfully by checking the plugin version.
- 6. Test critical functionality on the site to ensure the update did not cause issues.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Citadela Listing
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32085 — 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-2024-32085 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