Wp Seo PluginWordPress extension · Squirrly
CVE-2024-3679
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 Premium SEO Pack – WP SEO Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.6.002. This makes it possible for unauthenticated attackers to view limited information from password protected posts through the social meta data.
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 Premium SEO Pack WordPress plugin versions up to 1.6.002 contains a sensitive information exposure vulnerability in its social metadata functionality. Unauthenticated attackers can bypass password protection on posts to view limited information through the plugin's social meta data output.
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
Wp Seo PluginWordPress extension
<= 1.6.001CVSS 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.
-
Check if the Premium SEO Pack or Squirrly SEO plugin is installedNavigate to WordPress admin > Plugins and look for 'Premium SEO Pack' or 'Squirrly SEO' in the installed plugins list, or inspect the wp-content/plugins/ directory for a folder named 'squirrly-seo' or 'premium-seo-pack'Affected if The plugin is installed and active
-
Verify the installed plugin versionIn WordPress admin > Plugins, click on the plugin to view its details and locate the version number displayed thereAffected if The version is 1.6.001 or lower (the affected range)
-
Confirm social metadata features are enabledGo to the plugin settings in WordPress admin - look for Social Metadata, Open Graph, Twitter Cards, or Social Meta settings sections under the SEO plugin configurationAffected if Social metadata output functionality is enabled and exposed publicly
-
Identify password-protected postsIn WordPress admin > Posts, filter or search for posts with password protection enabled, or query the wp_posts table for posts where post_password is not emptyAffected if There are password-protected posts on the site that could be exposed through the social metadata leak
A user is affected if the Premium SEO Pack / Squirrly SEO plugin version 1.6.001 or lower is installed with social metadata features enabled on a site containing password-protected posts.
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 Premium SEO Pack plugin to a version beyond 1.6.002 if a patched version is available; otherwise, remove the plugin until a fix is released.
Fix this in Wp Seo Plugin
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3679 — 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-3679 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