CVE-2024-33575
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 User Meta user-meta.This issue affects User Meta: from n/a through 3.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 · low confidenceThe User Meta WordPress plugin (versions through 3.0) contains an information disclosure vulnerability that allows unauthorized actors to access sensitive information. The specific nature of the exposed data is not detailed in the available advisory, but such vulnerabilities in user management plugins typically involve improper access controls on user profile data, metadata, or administrative information.
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 User Meta plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'User Meta' in the list of active plugins.Affected if User Meta plugin appears in the installed plugins list, regardless of activation status
-
Check the installed version of User MetaIn the Plugins list, click on the User Meta plugin to view its details, or open wp-content/plugins/user-meta/readme.txt and locate the 'Stable tag' entry.Affected if The version listed is 3.0 or any version below 3.0 (for example 2.9, 2.8, etc.)
-
Identify public-facing user data endpointsReview the site for any pages or API endpoints that query user data. Common paths include /?author=ID, /wp-json/wp/v2/users, or custom endpoints added by the plugin.Affected if User profile pages or API endpoints are publicly accessible without authentication
-
Test for unauthorized user metadata accessUse a web browser or curl to request author archive pages or user profile URLs. Compare the response to confirm if sensitive user fields (such as email addresses, roles, or custom meta) are exposed to unauthenticated visitors.Affected if Sensitive user information is returned in the response for users who are not logged in
You are affected if the User Meta plugin version is 3.0 or lower AND unauthenticated visitors can access user profile data on your site.
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 User Meta plugin to the latest version once available, or implement proper access control checks on all user data endpoints. If the plugin is no longer maintained, consider migrating to an actively maintained alternative.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33575 — 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-33575 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