dbcve.org
Premium Seo PackWordPress extension · Squirrly

CVE-2024-50465

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 1.6.002 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WP SEO – Calin Vingan Premium SEO Pack allows SQL Injection.This issue affects Premium SEO Pack: from n/a through 1.6.001.

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

SQL injection vulnerability in the Premium SEO Pack WordPress plugin allows authenticated attackers to inject malicious SQL commands through unsanitized input parameters. The vulnerability exists in the plugin's handling of user-supplied data in SQL queries without proper parameterization.

MitigationUpdate to the latest patched version of Premium SEO Pack plugin. If no patched version is available, implement input validation using prepared statements/parameterized queries for all database operations and consider disabling the plugin until a fix is released.

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
Premium Seo PackWordPress extension
Affected:< 1.6.002

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Verify Squirrly Premium SEO Pack is installed
    Navigate to WordPress admin dashboard > Plugins and confirm Premium SEO Pack (Squirrly) appears in the installed plugins list. Note whether it is activated.
    Affected if Plugin is installed and active, making the vulnerable code accessible
  2. Check installed plugin version
    In WordPress admin > Plugins > Premium SEO Pack, view the plugin details to find the installed version number. Compare this version against the affected range: versions prior to 1.6.002 are vulnerable.
    Affected if Installed version is lower than 1.6.002
  3. Confirm authentication access exists
    Review user roles on the site (Users > All Users) to determine if any non-admin accounts exist. This vulnerability requires an authenticated attacker, so the presence of subscriber, contributor, or editor-level accounts increases exposure.
    Affected if Authenticated users (any role beyond administrator) exist on the site
  4. Inspect server logs for suspicious SQL patterns
    Review access logs (typically in /wp-content/debug.log or server access logs) for unusual SQL syntax or database errors around plugin endpoints. Search for patterns like UNION SELECT, OR 1=1, or other SQL keywords in query parameters.
    Affected if Logs show SQL injection attempts targeting plugin-related URLs or query parameters

The environment is affected if the Premium SEO Pack plugin is installed with a version lower than 1.6.002 and the site has authenticated user accounts that could trigger the vulnerable code path.

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.002 or later
Fixed in 1.6.002
Interim mitigation

Update to the latest patched version of Premium SEO Pack plugin. If no patched version is available, implement input validation using prepared statements/parameterized queries for all database operations and consider disabling the plugin until a fix is released.

Recommended fix Moderate confidence

1.6.002

  1. Backup your WordPress database and files before making any changes
  2. Update Premium SEO Pack plugin to version 1.6.002 or later via WordPress admin dashboard (Plugins > Updates)
  3. Alternatively, upload the updated plugin files manually via FTP or file manager
  4. Clear any caching mechanisms after updating
  5. Verify the plugin is functioning correctly and the SQL injection vulnerability is resolved

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

Fix this in Premium Seo Pack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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