dbcve.org
Seo Plugin By Squirrly SeoWordPress extension · Squirrly

CVE-2024-29790

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 12.3.17 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Squirrly SEO Plugin by Squirrly SEO allows Reflected XSS.This issue affects SEO Plugin by Squirrly SEO: from n/a through 12.3.16.

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 confidence

A reflected XSS vulnerability in the Squirrly SEO WordPress plugin (versions through 12.3.16) allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the web page response, potentially stealing session cookies or performing actions on behalf of authenticated users.

MitigationUpgrade to SEO Plugin by Squirrly SEO version 12.3.17 or later which addresses the improper input neutralization. Until patched, avoid clicking untrusted links to the affected site.

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
Seo Plugin By Squirrly SeoWordPress extension
Affected:< 12.3.17

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Squirrly SEO plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'SEO Plugin by Squirrly SEO' or check the wp-content/plugins/ directory for a folder named 'squirrly-seo' or similar Squirrly plugin folder
    Affected if The plugin is not found in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the Squirrly SEO plugin, and note the version number displayed beneath the plugin name
    Affected if Version is less than 12.3.17 (e.g., 12.3.16, 12.3.15, etc.)
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Squirrly SEO plugin shows as 'Active' rather than 'Inactive'
    Affected if Plugin is active and version is below 12.3.17
  4. Check for unknown or suspicious admin users
    Navigate to Users > All Users in WordPress admin and review the list for any unfamiliar administrator accounts that may have been created via the XSS vulnerability
    Affected if Unexpected admin accounts exist that you did not create

You are affected if the Squirrly SEO plugin is installed, active, and running a version lower than 12.3.17, making reflected XSS exploitation possible through the vulnerable input fields.

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 12.3.17 or later
Fixed in 12.3.17
Interim mitigation

Upgrade to SEO Plugin by Squirrly SEO version 12.3.17 or later which addresses the improper input neutralization. Until patched, avoid clicking untrusted links to the affected site.

Recommended fix High confidence

12.3.17

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Seo Plugin By Squirrly SEO' in the list
  4. Check if the current version is below 12.3.17
  5. If vulnerable, click 'Update Now' to upgrade to version 12.3.17 or later
  6. Alternatively, download version 12.3.17 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin

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

Fix this in Seo Plugin By Squirrly Seo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29790 — 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-29790 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