dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-48091

HIGH · 8.5 CVSS v3.1 Published 2025-10-22
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 Alexander AnyComment anycomment allows SQL Injection.This issue affects AnyComment: from n/a through <= 0.3.6.

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 AnyComment WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user input being incorporated into database queries. The vulnerability affects all versions up to and including 0.3.6, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationReplace dynamic SQL query construction with parameterized queries (prepared statements) or leverage the WordPress $wpdb methods with proper escaping/placeholder substitution for all user-supplied input before executing database queries.

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. Verify AnyComment plugin is installed
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, and look for AnyComment in the list of installed plugins.
    Affected if AnyComment plugin appears in the installed plugins list
  2. Check installed AnyComment version
    In the plugins list, locate AnyComment and view the version number displayed below the plugin name. Alternatively, check the main plugin file (anycomment.php) for the 'Version' header comment.
    Affected if The installed version is 0.3.6 or any version up to and including 0.3.6
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify that AnyComment shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if AnyComment is activated on the WordPress site
  4. Identify vulnerable code paths
    Examine the AnyComment plugin PHP files for direct SQL query construction using $wpdb->prepare without proper placeholder substitution, or $wpdb->query with string-concatenated user input. Focus on files handling comment submission or user data processing.
    Affected if The plugin code contains SQL queries built by concatenating user-supplied input directly into query strings without using prepared statements or proper escaping

A WordPress site is affected if AnyComment plugin version 0.3.6 or lower is installed and active, with unsanitized user input being processed through the plugin's database query functions.

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

Replace dynamic SQL query construction with parameterized queries (prepared statements) or leverage the WordPress $wpdb methods with proper escaping/placeholder substitution for all user-supplied input before executing database queries.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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