dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-15268

HIGH · 7.5 CVSS v3.1 Published 2026-02-04
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 Infility Global plugin for WordPress is vulnerable to unauthenticated SQL Injection via the 'infility_get_data' API action in all versions up to, and including, 2.14.46. 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 - with certain server configurations - 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 Infility Global WordPress plugin (versions up to 2.14.46) contains an unauthenticated SQL Injection vulnerability in the infility_get_data API action. Attackers can exploit insufficient input sanitization and lack of prepared statements in the SQL query to inject malicious SQL code and extract sensitive database information.

MitigationUpdate the Infility Global plugin to a version beyond 2.14.46 if available, or remove/disable the plugin until a patched version is released.

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. Confirm Infility Global plugin is installed
    Log into WordPress admin and go to Plugins > Installed Plugins, or run: wp plugin list --search='infility-global'
    Affected if The plugin appears in the list of installed plugins
  2. Identify the installed plugin version
    In WordPress admin plugin list, click on the plugin name details to see the version number; or run: wp plugin get infility-global --field=version
    Affected if The version number is 2.14.46 or lower (any version up to and including 2.14.46)
  3. Check if the vulnerable API endpoint is accessible
    Send a GET request to the REST API endpoint: /wp-json/infility_get_data (or /?rest_route=/infility_get_data) using curl or a browser without authentication
    Affected if The endpoint returns any HTTP response (even an error) rather than a 401/403 authentication failure, indicating the endpoint exists and is reachable
  4. Test for unauthenticated access to the API action
    Send a POST request to the endpoint with a minimal payload such as action=get_data without any authentication headers, e.g., curl -X POST https://yourdomain.com/wp-json/infility_get_data -d 'action=get_data'
    Affected if The server accepts the request without requiring authentication (response is not 401 or 403)

You are affected if the Infility Global plugin is installed with version 2.14.46 or lower AND the infility_get_data REST API endpoint is accessible without authentication.

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 Infility Global plugin to a version beyond 2.14.46 if available, or remove/disable the plugin until a patched version is released.

Recommended fix Moderate confidence

Version 2.14.47 or later

  1. Update the Infility Global WordPress plugin to the latest available version
  2. If automatic updates are enabled, verify the update has been applied
  3. Confirm the site is running a version newer than 2.14.46 after updating
  4. Test that the infility_get_data API functionality works correctly post-update

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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