# CVE-2026-116182: phpMyFAQ before 4.1.10 SSRF via PDF Export Image Fetching


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-8wmv-9c4g-p5mg, GHSA-qxg5-vwcr-vrfc

## What is CVE-2026-116182?

CVE-2026-116182 is a medium-severity vulnerability in thorsten phpMyFAQ, published on 25 Oct 2026. 

### Official description

phpMyFAQ before 4.1.10 contains a server-side request forgery vulnerability in the PDF export feature that fetches external images referenced in FAQ answers. Attackers who can influence FAQ content can embed image URLs pointing to loopback or internal services, causing the server to request them and embed responses in generated PDFs.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-116182?


## How do I fix CVE-2026-116182?

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

## Is CVE-2026-116182 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116182 and fix it if it is affected.

What it is: CVE-2026-116182 is a medium-severity vulnerability in thorsten phpMyFAQ, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116182 exists.

Affected product: thorsten phpMyFAQ. 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-2026-116182/ (Markdown: https://insights.sbomify.com/CVE-2026-116182/index.md)
```

## Sources

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

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