# CVE-2016-20101: Issuu Panel WordPress Plugin < 1.6.6 File Inclusion via ajax-docs.php


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-788p-94rp-c28h

## What is CVE-2016-20101?

CVE-2016-20101 is a critical vulnerability in Pedro Marcelo Issuu Panel, published on 20 Oct 2026. 

### Official description

Issuu Panel plugin for WordPress before 1.6.6 contains a PHP file inclusion vulnerability that allows unauthenticated attackers to include remote or local files through the 'abspath' parameter. Attackers can send GET requests to menu/documento/requests/ajax-docs.php with a crafted abspath value passed to require() to execute remote PHP code or include local files. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-20.

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

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


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

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

## Is CVE-2016-20101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-20101 is a critical vulnerability in Pedro Marcelo Issuu Panel, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20101 exists.

Affected product: Pedro Marcelo Issuu Panel. 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-20101/ (Markdown: https://insights.sbomify.com/CVE-2016-20101/index.md)
```

## Sources

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

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