How severe is GHSA-x769-3cwv-f8hc?

No CVSS score has been assigned to GHSA-x769-3cwv-f8hc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x769-3cwv-f8hc?

GHSA-x769-3cwv-f8hc affects the following packages: in2code/powermail (Packagist), in2code/powermail (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-x769-3cwv-f8hc?

Update in2code/powermail to 12.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x769-3cwv-f8hc is resolved across your whole dependency graph.

How do I detect GHSA-x769-3cwv-f8hc in my Packagist dependencies?

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

How do I mitigate GHSA-x769-3cwv-f8hc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-x769-3cwv-f8hc?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-x769-3cwv-f8hc can be triaged on real exposure rather than presence alone.

Is GHSA-x769-3cwv-f8hc actively exploited in the wild?

No public exploit code has been indexed for GHSA-x769-3cwv-f8hc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x769-3cwv-f8hc?

GHSA-x769-3cwv-f8hc has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th 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-x769-3cwv-f8hc?

GHSA-x769-3cwv-f8hc is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-x769-3cwv-f8hc published, and has it been updated?

GHSA-x769-3cwv-f8hc was published on July 22, 2025 and was last updated on July 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-x769-3cwv-f8hc — in2code/powermail

Fix: in2code-de/powermail@b39e129

GHSA-x769-3cwv-f8hc is a CWE-639 vulnerability in in2code/powermail. A fix is available for in2code/powermail — see the affected versions and patch details below.

Powermail extension for TYPO3 allows Insecure Direct Object Reference

Also known asCVE-2025-7899

Published

Jul 22, 2025

Updated

Jul 22, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-x769-3cwv-f8hc.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐘in2code/powermail🐘in2code/powermail

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

Description

The powermail extension for TYPO3 allows Insecure Direct Object Reference resulting in download of arbitrary files from the webserver. This issue affects powermail version 12.0.0 up to 12.5.2 and version 13.0.0.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`in2code/powermail`	≥ 12.0.0&&< 12.5.3	12.5.3`composer require in2code/powermail:^12.5.3`
🐘Packagist	`in2code/powermail`	≥ 13.0.0&&< 13.0.1	13.0.1`composer require in2code/powermail:^13.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/powermail, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update in2code/powermail to 12.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x769-3cwv-f8hc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-x769-3cwv-f8hc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-x769-3cwv-f8hc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-x769-3cwv-f8hc in your dependencies?

O3 Security finds GHSA-x769-3cwv-f8hc across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works