dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-28136

HIGH · 7.6 CVSS v3.1 Published 2026-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 VeronaLabs WP SMS wp-sms allows SQL Injection.This issue affects WP SMS: from n/a through <= 6.9.12.

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 VeronaLabs WP SMS plugin (wp-sms) versions up to 6.9.12 allows attackers to inject malicious SQL commands via improper neutralization of special elements in SQL queries. This could enable unauthorized database access, data exfiltration, or manipulation.

MitigationUpgrade WP SMS plugin to version 6.9.13 or later which contains the security fix. Until then, restrict administrative access and monitor for suspicious database query patterns.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 wp-sms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP SMS' by VeronaLabs, or check the /wp-content/plugins/ directory for the wp-sms folder
    Affected if The plugin is present in the WordPress installation
  2. Check installed wp-sms version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the WP SMS plugin description, or read the main plugin file header in /wp-content/plugins/wp-sms/wp-sms.php for the 'Version' tag
    Affected if Version is 6.9.12 or lower (any version up to and including 6.9.12)
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the WP SMS plugin shows 'Active' status rather than 'Inactive'
    Affected if Plugin is currently active and exposed to requests
  4. Identify exposed endpoints
    Check for publicly accessible WordPress REST API endpoints or admin AJAX actions related to wp-sms (typically under /wp-json/wp-sms/ or admin-ajax.php?action=wp_sms), or review the plugin settings for any exported functionality
    Affected if Unauthenticated or low-privilege users can trigger the SQL query functions

User is affected if the wp-sms plugin version is 6.9.12 or lower and the plugin is active with accessible SQL query endpoints

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

Upgrade WP SMS plugin to version 6.9.13 or later which contains the security fix. Until then, restrict administrative access and monitor for suspicious database query patterns.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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