dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30775

HIGH · 8.5 CVSS v3.1 Published 2025-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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 AmentoTech Private Limited WPGuppy wpguppy-lite allows SQL Injection.This issue affects WPGuppy: from n/a through <= 1.1.3.

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 WPGuppy wpguppy-lite plugin allows attackers to inject malicious SQL commands via unsanitized input in the plugin. With a CVSS score of 8.5, this high-severity flaw could allow unauthorized database access, data exfiltration, or privilege escalation.

MitigationUpdate WPGuppy to the latest patched version; if no patch available, disable the plugin until remediation. For immediate workarounds, implement input validation and web application firewall rules to block SQL injection attempts.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

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. Confirm WPGuppy lite plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WPGuppy Lite' or 'wpguppy-lite' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find WPGuppy Lite, and note the version number displayed below the plugin name
    Affected if A version number is displayed and can be compared to the patched version
  3. Verify the plugin handles user-supplied input
    Inspect the plugin settings or any public-facing features that accept user input (search fields, form submissions, URL parameters). SQL injection requires unsanitized input to be passed to database queries.
    Affected if The plugin accepts user input through search parameters, forms, or URL arguments that could be manipulated
  4. Check for signs of SQL injection exploitation
    Review WordPress debug logs (wp-content/debug.log if enabled), server access logs, and database query logs for suspicious SQL syntax or unusual database activity originating from the plugin's endpoints
    Affected if Unusual SQL patterns, error messages containing database structure information, or unexpected data access patterns are found in logs

A user is affected if they have WPGuppy Lite installed and the installed version predates the patched release, especially if the plugin accepts user input through unsanitized parameters.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WPGuppy to the latest patched version; if no patch available, disable the plugin until remediation. For immediate workarounds, implement input validation and web application firewall rules to block SQL injection attempts.

Have this fixed 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 help mitigating

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-2025-30775 — 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-2025-30775 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