How severe is GHSA-ff3m-68vj-h86p?

GHSA-ff3m-68vj-h86p has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-ff3m-68vj-h86p?

GHSA-ff3m-68vj-h86p affects the following packages: net.sourceforge.plantuml:plantuml-mit (Maven), net.sourceforge.plantuml:plantuml (Maven). Ecosystems affected: Maven.

How do I fix GHSA-ff3m-68vj-h86p?

Update net.sourceforge.plantuml:plantuml-mit to 1.2023.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ff3m-68vj-h86p is resolved across your whole dependency graph.

How do I detect GHSA-ff3m-68vj-h86p in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sourceforge.plantuml:plantuml-mit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-ff3m-68vj-h86p if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-ff3m-68vj-h86p actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-ff3m-68vj-h86p, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-ff3m-68vj-h86p?

GHSA-ff3m-68vj-h86p has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-ff3m-68vj-h86p?

GHSA-ff3m-68vj-h86p is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-ff3m-68vj-h86p published, and has it been updated?

GHSA-ff3m-68vj-h86p was published on June 27, 2023 and was last updated on February 20, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

PlantUML Server-Side Request Forgery vulnerabilityGHSA-ff3m-68vj-h86p

HIGHFix: plantuml/plantuml@b32500b

GHSA-ff3m-68vj-h86p is a high-severity (CVSS 7.2) Server-Side Request Forgery (SSRF) vulnerability in net.sourceforge.plantuml:plantuml-mit. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for net.sourceforge.plantuml:plantuml-mit — see the affected versions and patch details below.

Also known asCVE-2023-3432

Published

Jun 27, 2023

Updated

Feb 20, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕net.sourceforge.plantuml:plantuml-mit☕net.sourceforge.plantuml:plantuml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Server-Side Request Forgery (SSRF) in GitHub repository plantuml/plantuml prior to 1.2023.9.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.sourceforge.plantuml:plantuml-mit`	all versions	1.2023.9`net.sourceforge.plantuml:plantuml-mit:1.2023.9`
☕Maven	`net.sourceforge.plantuml:plantuml`	all versions	1.2023.9`net.sourceforge.plantuml:plantuml:1.2023.9`

Affected Products

2 products · 2 configurations

fedorafedoraproject

1 version

Application

plantumlplantuml

< 1.2023.9

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Server-Side Request Forgery (SSRF) in GitHub repository plantuml/plantum…

huntr.devNVDJul 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sourceforge.plantuml:plantuml-mit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.sourceforge.plantuml:plantuml-mit to 1.2023.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ff3m-68vj-h86p is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

Server-Side Request Forgery (SSRF) in GitHub repository plantuml/plantuml prior to 1.2023.9.

O3 Security · Impact-Aware SCA

Is GHSA-ff3m-68vj-h86p in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.2/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jun 27, 2023

First exploit

Jul 3, 2023

6 days after disclosure — rapid exploitation

Last updated

Feb 20, 2024

Identifiers

GHSA-ff3m-68vj-h86p

References

Advisorynvd.nist.gov · CVE 2023 3432 Webgithub.com · b32500bb61ae617bb312496d6d832e4be8190797 Webhuntr.dev · 8ac3316f 431c 468d 87e4 3dafff2ecf51 Weblists.fedoraproject.org · FV7XL3CY3K3K5ER3ASMEQA546MIQQ7QM Packagegithub.com · plantuml

Related vulnerabilities

Also affects plantuml-mit

This CVE is high severity; 1 of 2 other CVEs affecting plantuml-mit is rated as high or higher (top: high).

CVE-2023-3432CVE-2023-3431

Also affects plantuml

This CVE is high severity — higher than any of the other 1 CVE affecting plantuml (highest there: low).

CVE-2026-0858

Same weakness: CWE-918

This CVE is high severity — higher than any of the other 5 CVEs with CWE-918 (highest there: moderate).

CVE-2026-126062CVE-2026-79914CVE-2026-88983CVE-2026-28385GHSA-7wpf-ch8f-5f4xBrowse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 20, 2024

PlantUML Server-Side Request Forgery vulnerabilityGHSA-ff3m-68vj-h86p

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-ff3m-68vj-h86p in your dependencies?