dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-8685

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-20
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 Infility Global plugin for WordPress is vulnerable to SQL Injection via the 'orderby' and 'order' parameters in all versions up to, and including, 2.15.16. This is due to insufficient escaping on user supplied parameters and lack of sufficient preparation on the existing SQL query within the show_control_data::post_list() function, which is registered as an admin menu page with only the 'read' capability. This makes it possible for authenticated attackers, with Subscriber-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 Infility Global WordPress plugin (versions ≤2.15.16) contains a SQL Injection vulnerability in the show_control_data::post_list() function accessible via an admin menu page. Authenticated attackers with Subscriber-level access (or higher) can inject malicious SQL queries through the 'orderby' and 'order' parameters due to insufficient input sanitization and missing prepared statement usage in the underlying SQL query.

MitigationUpdate the Infility Global plugin to version 2.15.17 or later which includes proper input escaping and prepared statements. If an update is unavailable, disable the plugin immediately to prevent database exposure.

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 Infility Global plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Infility Global', or check for the plugin directory at wp-content/plugins/infility-global/
    Affected if The plugin is not present in the WordPress installation
  2. Identify the installed plugin version
    View the plugin version in the WordPress plugins list page, or open the main plugin PHP file (usually infility-global.php) and check the 'Version' header in the plugin comment block
    Affected if Version is 2.15.16 or lower (any version up to and including 2.15.16)
  3. Locate the vulnerable post_list function
    Examine the plugin source code for a class named show_control_data containing a method named post_list(), and verify if it directly uses $_GET['orderby'] or $_GET['order'] parameters in the SQL query
    Affected if The post_list() function exists and uses orderby/order GET parameters without prepared statements or proper escaping
  4. Verify access control on the vulnerable function
    Review the plugin AJAX handlers or direct function calls to determine if the post_list() function can be accessed by users with Subscriber-level permissions or higher
    Affected if The vulnerable endpoint is accessible to authenticated users with Subscriber role or higher

The environment is affected if the Infility Global plugin version is 2.15.16 or lower and the show_control_data::post_list() function handles orderby/order parameters without parameterized queries.

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 version 2.15.17 or later which includes proper input escaping and prepared statements. If an update is unavailable, disable the plugin immediately to prevent database exposure.

Recommended fix Moderate confidence

Infility Global version 2.15.17 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Infility Global' plugin
  4. Check if an update to version 2.15.17 or later is available
  5. If an update is available, click 'Update Now' to install the patched version
  6. If no automatic update is available, manually download version 2.15.17 or later from the WordPress plugin repository and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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