dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-13077

HIGH · 7.5 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The افزونه پیامک ووکامرس فوق حرفه ای (جدید) payamito sms woocommerce plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'columns' parameter in all versions up to, and including, 1.3.5. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 · high confidence

The payamito SMS WooCommerce WordPress plugin versions up to 1.3.5 contain a time-based blind SQL injection vulnerability in the 'columns' parameter. Due to insufficient input sanitization and lack of prepared statements in the SQL query, unauthenticated attackers can inject arbitrary SQL queries to extract sensitive data from the database using time-based inference techniques.

MitigationUpdate the payamito SMS woocommerce plugin to version 1.3.6 or later. If updates are unavailable, disable the plugin until a patched version is released. Alternatively, implement proper input validation and prepared statements in the code to remediate the SQL injection.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 payamito SMS WooCommerce plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'payamito SMS WooCommerce' in the list. Note the installed version displayed.
    Affected if Plugin is present in the WordPress installation
  2. Check the installed plugin version
    In the plugins list, read the version number displayed beneath the plugin name. Compare this version against the affected range (1.3.5 and below).
    Affected if Version is 1.3.5 or lower (versions up to and including 1.3.5 are vulnerable)
  3. Confirm the vulnerable parameter endpoint is accessible
    Identify if the plugin exposes functionality that accepts a 'columns' parameter in HTTP requests. This typically occurs in AJAX endpoints or front-end AJAX actions used by the plugin.
    Affected if The plugin endpoint accepting the 'columns' parameter is accessible to unauthenticated users
  4. Verify lack of input validation on the columns parameter
    If accessible, inspect HTTP requests to the plugin that include the 'columns' parameter. The vulnerability exists because this parameter is not sanitized before being used in SQL queries.
    Affected if The 'columns' parameter is processed without prepared statements or input sanitization in the underlying SQL query

If the installed plugin version is 1.3.5 or lower and the plugin is active, the environment is affected by this SQL injection vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the payamito SMS woocommerce plugin to version 1.3.6 or later. If updates are unavailable, disable the plugin until a patched version is released. Alternatively, implement proper input validation and prepared statements in the code to remediate the SQL injection.

Recommended fix Moderate confidence

Latest version after 1.3.5 (check WordPress plugin repository for current stable release)

  1. Check the current version of the payamito SMS woocommerce plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate 'افزونه پیامک ووکامرس پیامیتو' (payamito sms woocommerce) and note the current version
  4. Update the plugin to the latest available version from the WordPress plugin repository
  5. After updating, verify the plugin functions correctly with your WooCommerce SMS notifications
  6. Consider reviewing the plugin's settings to ensure configuration is intact after the update
Caveat Minor: Review plugin settings after upgrade to ensure SMS notification configuration is intact

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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