CVE-2024-47344
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 Stylemix uListing ulisting.This issue affects uListing: from n/a through <= 2.1.5.
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 confidenceThe uListing WordPress plugin versions 2.1.5 and below contains an information disclosure vulnerability allowing unauthorized access to sensitive data. The issue stems from improper access controls that fail to restrict sensitive endpoint access to authorized users, potentially exposing listing data, user information, or configuration details to unauthenticated or lower-privileged 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm uListing plugin is installedLocate the uListing plugin in your WordPress installation's plugin directory or check via WordPress admin dashboard under PluginsAffected if The plugin is present and no recent security updates have been applied
-
Identify installed uListing versionCheck the plugin header in the main uListing PHP file or the plugin details page in WordPress admin for the current version numberAffected if The installed version is 2.1.5 or any version below 2.1.5
-
Enumerate uListing REST API endpointsUse a tool to probe the WordPress REST API for routes prefixed with ulisting, such as /wp-json/ulisting/v1/ or similar endpoint patternsAffected if Unauthenticated or low-privilege endpoints are accessible that should require higher permissions
-
Test endpoint access without authenticationSend HTTP requests to known uListing data endpoints without providing authentication credentials to verify if sensitive data is returnedAffected if The server returns listing data, user information, or configuration details to unauthenticated requests
-
Test endpoint access with low-privilege userLog in with a subscriber-level or contributor-level user account and attempt to access admin-level or data-serving endpointsAffected if Lower-privileged users can view data intended only for administrators
Your environment is affected if uListing version 2.1.5 or below is installed AND sensitive endpoints are accessible to unauthenticated or lower-privileged users without proper capability validation.
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 uListing to the latest version (if available) or implement proper capability checks and access controls on all sensitive endpoints. If no patch exists, restrict access to admin-only functionality via WordPress capability checks and ensure all data-serving endpoints validate user permissions before returning any information.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47344 — 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-47344 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