dbcve.org
Easy SeoWordPress extension · Boldgrid

CVE-2024-2950

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-06
Fix available
A fix is available. Upgrade to 1.6.15 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The BoldGrid Easy SEO – Simple and Effective SEO plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.6.14 via meta information (og:description) This makes it possible for unauthenticated attackers to view the first 130 characters of a password protected post which can contain sensitive information.

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 confidence

The BoldGrid Easy SEO plugin for WordPress exposes the first 130 characters of password-protected posts through Open Graph meta tags (og:description). Unauthenticated attackers can retrieve sensitive information from protected content via this information disclosure vector.

MitigationUpdate the BoldGrid Easy SEO plugin to version 1.6.15 or later which includes proper checks to prevent og:description from being rendered for password-protected posts.

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
Easy SeoWordPress extension
Affected:< 1.6.15

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify BoldGrid Easy SEO is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'BoldGrid Easy SEO' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'boldgrid-easy-seo' or check the plugin's main PHP file header for the plugin name.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the BoldGrid Easy SEO entry. The version number is displayed below the plugin name. Alternatively, open the main plugin file (such as boldgrid-easy-seo.php) and look for the 'Version' header in the plugin comment block.
    Affected if The version is lower than 1.6.15 (e.g., 1.6.14, 1.6.13, etc.)
  3. Identify password-protected posts
    Query the WordPress database: SELECT ID, post_title, post_password FROM wp_posts WHERE post_password != '' AND post_status = 'publish'; (table prefix may vary). Or use WordPress admin by going to Posts and looking for posts with a lock icon indicating password protection.
    Affected if There are published posts with password protection enabled on the site
  4. Inspect og:description meta tag for protected content
    Visit a password-protected post URL while logged out (as an unauthenticated user). View the page source (right-click > View Page Source) and search for '<meta property="og:description"'. Check if content from the protected post appears in the content attribute.
    Affected if The og:description meta tag contains text from a password-protected post to unauthenticated visitors

If BoldGrid Easy SEO version is below 1.6.15 AND password-protected posts exist on the site, the vulnerability is present and sensitive content may be exposed via Open Graph meta tags.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.6.15 or later
Fixed in 1.6.15
Interim mitigation

Update the BoldGrid Easy SEO plugin to version 1.6.15 or later which includes proper checks to prevent og:description from being rendered for password-protected posts.

Recommended fix High confidence

Easy Seo version 1.6.15

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'BoldGrid Easy SEO' or 'Easy Seo' plugin in the list
  4. Click 'Update now' if an update is available, or click 'Delete' and reinstall version 1.6.15
  5. Verify the plugin version is 1.6.15 after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Easy Seo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2950 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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