dbcve.org
Nelio Ab TestingWordPress extension · Neliosoftware

CVE-2016-10927

CRITICAL · 10.0 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 4.5.11 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.11 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.11 contains a Server-Side Request Forgery (SSRF) vulnerability in the ajax/iesupport.php file. This allows attackers to make the server perform requests to arbitrary URLs, potentially accessing internal services or bypassing network restrictions.

MitigationUpdate the nelio-ab-testing plugin to version 4.5.11 or later. If immediate update is not possible, deactivate and remove the plugin until the patch can be applied.

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.11

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. Verify Nelio Ab Testing plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Nelio A/B Testing' or 'nelio-ab-testing' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'nelio-ab-testing'.
    Affected if The plugin is installed and active on the WordPress site.
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find the Nelio A/B Testing plugin and read the version number displayed below the plugin name. Alternatively, open /wp-content/plugins/nelio-ab-testing/readme.txt and locate the 'Stable tag' or version line.
    Affected if The version number is less than 4.5.11 (e.g., 4.5.10, 4.5.9, etc.).
  3. Confirm vulnerable file exists
    Check if the file /wp-content/plugins/nelio-ab-testing/ajax/iesupport.php exists on the server. Access it via the browser at yoursite.com/wp-admin/admin-ajax.php?action=iesupport or directly if accessible.
    Affected if The file ajax/iesupport.php exists in the plugin directory.
  4. Verify SSRF vulnerability is reachable
    Attempt a simple request to the vulnerable endpoint. The ajax/iesupport.php file accepts a parameter (typically 'url' or similar) that allows arbitrary URL injection. If the endpoint responds without proper authentication, the vulnerability is reachable.
    Affected if The endpoint responds and accepts a URL parameter without requiring authentication or proper validation.

A user is affected if the Nelio Ab Testing plugin version is below 4.5.11 AND the ajax/iesupport.php file exists and is accessible on the server.

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.11 or later
Fixed in 4.5.11
Interim mitigation

Update the nelio-ab-testing plugin to version 4.5.11 or later. If immediate update is not possible, deactivate and remove the plugin until the patch can be applied.

Recommended fix High confidence

Nelio A/B Testing version 4.5.11

  1. Backup your WordPress database and files before making any changes
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find 'Nelio A/B Testing' in the plugin list
  5. Click 'Update now' to update the plugin to version 4.5.11, or manually upload the 4.5.11 version if automatic update is not available
  6. After update completes, verify the installed version is 4.5.11 or higher
  7. Test that the plugin functionality works correctly on your site
  8. Confirm the ajax/iesupport.php endpoint is no longer vulnerable to SSRF
Caveat Minor: As with any plugin update, test in staging environment first; no major breaking changes reported for this version

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

Fix this in Nelio Ab Testing Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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