CVE-2024-2795
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 · uneditedThe SEO SIMPLE PACK plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 3.2.1 via META description. This makes it possible for unauthenticated attackers to extract limited information about password protected posts.
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 · high confidenceThe SEO SIMPLE PACK WordPress plugin fails to properly restrict access to META description data for password-protected posts, allowing unauthenticated attackers to extract limited information about such posts by requesting the meta description through the plugin's functionality.
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.
-
Verify SEO SIMPLE PACK plugin is installedCheck your WordPress installation for the SEO SIMPLE PACK plugin in wp-content/plugins/ or via the WordPress admin plugin listAffected if The plugin is installed and active
-
Identify the installed plugin versionLocate the main plugin file (usually seo-simple-pack.php or similar) and read the version header comment, or check via WordPress admin plugin pageAffected if Version is lower than 3.2.2 (vulnerable versions)
-
Confirm password-protected posts exist with plugin-set meta descriptionsQuery your WordPress database for posts with post_password set (password-protected) and check if the plugin stores meta description data for them, or review post settings in WordPress adminAffected if Password-protected posts exist and the plugin is used to set meta descriptions for those posts
-
Test unauthenticated meta description accessWith the plugin active and a password-protected post in place, attempt an unauthenticated request to the plugin's functionality that returns meta description data (such as checking the meta description output or API endpoint the plugin provides for SEO data)Affected if Meta description content for password-protected posts is returned without requiring password authentication
You are affected if SEO SIMPLE PACK plugin versions below 3.2.2 are installed and you have password-protected posts with meta descriptions managed by this plugin, since unauthenticated attackers could access that metadata.
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 · scopedUpdate the SEO SIMPLE PACK plugin to version 3.2.2 or later, which implements proper access controls for password-protected post metadata. Until then, consider disabling the plugin or restricting access to the affected functionality.
Latest version of SEO SIMPLE PACK plugin (version 3.2.2 or higher)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'SEO SIMPLE PACK' in the plugin list
- Check if an update is available and update to the latest version
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2795 — 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-2795 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