dbcve.org
Nelio Ab TestingWordPress extension · Neliosoftware

CVE-2016-10926

CRITICAL · 10.0 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 4.5.9 or later.
See remediation →
100/100
Remediation priority · Urgent
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 nelio-ab-testing plugin before 4.5.9 for WordPress has SSRF in ajax/iesupport.php.

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 nelio-ab-testing WordPress plugin before version 4.5.9 contains a Server-Side Request Forgery (SSRF) vulnerability in the ajax/iesupport.php file. This allows attackers to make the WordPress server perform arbitrary requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or bypassing network restrictions.

MitigationUpdate the nelio-ab-testing plugin to version 4.5.9 or later to remediate this SSRF vulnerability. If immediate update is not possible, consider restricting access to the vulnerable ajax endpoint via web server configuration or disabling the plugin until update is feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nelio Ab TestingWordPress extension
Affected:< 4.5.9

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
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 the Nelio Ab Testing plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Nelio Ab Testing' in the installed plugins list, or inspect the /wp-content/plugins/ directory for a folder named 'nelio-ab-testing'
    Affected if The plugin folder nelio-ab-testing exists in the plugins directory
  2. Identify the installed plugin version
    In WordPress Admin > Plugins, find the Nelio Ab Testing plugin and check the version number displayed below the plugin name, or open the main plugin file (typically nelio-ab-testing.php) and look for the 'Version' header comment
    Affected if The reported version number is lower than 4.5.9
  3. Verify the vulnerable ajax file exists
    Check if the file /wp-content/plugins/nelio-ab-testing/ajax/iesupport.php exists on the server filesystem
    Affected if The file ajax/iesupport.php exists in the plugin directory
  4. Confirm the plugin is active
    In WordPress Admin > Plugins, check whether Nelio Ab Testing is currently activated. Alternatively, query the WordPress options table for the active_plugins option
    Affected if The plugin is installed, vulnerable version, and currently active (making the SSRF endpoint accessible)

You are affected if the Nelio Ab Testing plugin is installed with a version lower than 4.5.9 and the ajax/iesupport.php file is present and accessible.

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
Upgrade available Upgrade to 4.5.9 or later
Fixed in 4.5.9
Interim mitigation

Update the nelio-ab-testing plugin to version 4.5.9 or later to remediate this SSRF vulnerability. If immediate update is not possible, consider restricting access to the vulnerable ajax endpoint via web server configuration or disabling the plugin until update is feasible.

Recommended fix High confidence

4.5.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Nelio A/B Testing plugin in the list
  4. Check the current version number - if it is less than 4.5.9, an update is needed
  5. Click 'Update Now' to upgrade to the latest version (4.5.9 or higher)
  6. Alternatively, download the plugin from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. Verify the installed version shows 4.5.9 or later after updating

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

Fix this in Nelio Ab Testing Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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