CVE-2024-32086
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in AitThemes Citadela Listing.This issue affects Citadela Listing: from n/a through 5.18.1.
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 confidenceCitadela Listing WordPress plugin versions up to 5.18.1 contain an information disclosure vulnerability allowing unauthorized actors to access sensitive data. The vulnerability stems from improper authorization checks on certain functionality, potentially exposing configuration details, user data, or listing information to unauthenticated users.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Citadela Listing plugin is installedNavigate to WordPress admin > Plugins and confirm Citadela Listing appears in the installed plugins list, or inspect the directory wp-content/plugins/ for a citadela-listing folderAffected if The plugin is installed and active in WordPress
-
Check installed version against affected rangeView the plugin version in the WordPress plugin admin page, or open wp-content/plugins/citadela-listing/readme.txt and locate the 'Stable tag' or 'Version' fieldAffected if The installed version is 5.18.1 or any earlier version (versions prior to the fix)
-
Identify exposed REST API endpointsAccess your site's REST API at /wp-json/ and look for routes under /wp-json/citadela-listing/ or similar paths; attempt to access these endpoints without authentication using a tool like curl or browser developer toolsAffected if Sensitive REST endpoints under the Citadela namespace return data without requiring authentication
-
Test AJAX action accessibilityInspect JavaScript files in the plugin for admin-ajax.php actions containing 'citadela', then attempt to call these actions without being logged in using a request to admin-ajax.php with the appropriate action parameterAffected if AJAX actions return sensitive listing, configuration, or user data to unauthenticated requests
A user is affected if Citadela Listing plugin versions up to 5.18.1 are installed and sensitive endpoints or AJAX actions are accessible without authentication verification.
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 Citadela Listing to the latest version available from the vendor, or implement proper authorization checks on all sensitive endpoints/functions if a patch is not available. Restrict access to sensitive data by verifying user capabilities before serving requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32086 — 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-32086 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