# CVE-2026-59231: Server-Side Request Forgery in Pentestify PDF export via unvalidated image URLs

> Authenticated users can trigger server-side HTTP requests to arbitrary destinations via unvalidated image URLs in Pentestify PDF exports.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-pj83-6473-35pq

## What is CVE-2026-59231?

CVE-2026-59231 is a medium-severity server-side request forgery vulnerability in ccyl13 Pentestify, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-Side Request Forgery in the PDF export component in maalfer Pentestify before 1.1.0 allows authenticated users to cause outbound HTTP GET requests from the server to arbitrary attacker-chosen destinations via unvalidated URLs stored in the finding images field or the report client_logo field, which the server-side headless browser fetches while rendering the report.

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

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


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

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

## Is CVE-2026-59231 being exploited?

There is no known exploitation of CVE-2026-59231 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59231 is a medium-severity server-side request forgery vulnerability in ccyl13 Pentestify, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59231 in the wild and no public exploit code.

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

## Sources

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

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