dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-9441

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The iATS Online Forms plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order' parameter in all versions up to, and including, 1.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, 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 iATS Online Forms WordPress plugin has a time-based SQL Injection vulnerability in the 'order' parameter through version 1.2. The vulnerability stems from insufficient input sanitization combined with the absence of prepared SQL statements, allowing authenticated users with Contributor-level access or higher to inject malicious SQL queries via the unsanitized parameter.

MitigationUpdate to the latest version of the iATS Online Forms plugin; if no update is available, implement proper input validation and replace dynamic SQL with $wpdb->prepare() using parameterized 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
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. Confirm iATS Online Forms plugin is installed
    Log into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'iATS Online Forms' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'iats-online-forms' or similar.
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In WordPress admin_plugins page, click on the plugin name to view details, or open the main plugin file (usually index.php or main PHP file in the plugin folder) and look for the version comment/header.
    Affected if The installed version is 1.2 or lower (including unversioned installations)
  3. Verify the order parameter is processed
    Examine the plugin code for handling of the 'order' parameter. Look for files that process $_GET or $_REQUEST['order'] and construct SQL queries without using $wpdb->prepare(). Search the plugin folder for SQL query patterns like 'ORDER BY' concatenated with request parameters.
    Affected if The plugin processes an 'order' parameter from user input and uses it in SQL queries without prepared statements
  4. Confirm user role access to vulnerable functionality
    In WordPress admin, go to Users > All Users and review which users have roles of Contributor or higher. Check if the iATS Online Forms plugin exposes any public-facing forms that accept the 'order' parameter without authentication.
    Affected if Any user with Contributor role or higher exists, or the vulnerable parameter is accessible to unauthenticated users (if the plugin exposes such endpoints)

If the iATS Online Forms plugin version is 1.2 or lower and processes the 'order' parameter in SQL queries without prepared statements, 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 to the latest version of the iATS Online Forms plugin; if no update is available, implement proper input validation and replace dynamic SQL with $wpdb->prepare() using parameterized queries.

Recommended fix Moderate confidence

Any version newer than 1.2 (check WordPress plugin repository for latest release)

  1. Check the current version of the iATS Online Forms plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is 1.2 or below, update the plugin to the latest available version from the WordPress plugin repository
  4. After updating, verify the plugin is working correctly on your site
  5. Ensure any users with Contributor-level or higher access are trusted, as this vulnerability requires authentication to exploit

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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