# CVE-2016-20082: WordPress Plugin Abtest Local File Inclusion via abtest_admin.php

> Unauthenticated attackers can execute arbitrary code via local file inclusion in the Abtest WordPress plugin by manipulating the action parameter.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-qgcw-xhvq-jg68

## What is CVE-2016-20082?

CVE-2016-20082 is a medium-severity path traversal vulnerability in Abtest, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WordPress Plugin Abtest contains a local file inclusion vulnerability that allows unauthenticated attackers to include arbitrary files by manipulating the action parameter. Attackers can send GET requests to abtest_admin.php with malicious action values to include files from the admin directory and execute arbitrary code.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2016-20082?


## How do I fix CVE-2016-20082?

No fix has been published for CVE-2016-20082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-20082 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20082 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20082 and fix it if it is affected.

What it is: CVE-2016-20082 is a medium-severity path traversal vulnerability in Abtest, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20082 exists.

Affected product: Abtest. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-20082/ (Markdown: https://insights.sbomify.com/CVE-2016-20082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-20082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-20082
- OSV: https://osv.dev/vulnerability/CVE-2016-20082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-20082/
Summaries are generated and may contain mistakes; the official description above is the record.