Is froxlor/froxlor affected by CVE-2026-41231?

Packagist froxlor/froxlor is affected in <2.3.6.

Is CVE-2026-41231 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.4%.

high

CVE-2026-41231

Q: Is CVE-2026-41231 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.4%.

Packagist · froxlor/froxlor

Summary

Froxlor has Incomplete Symlink Validation in DataDump.add() Allows Arbitrary Directory Ownership Takeover via Cron

Severity: high
EPSS: 0.4% (p33)
Also known as: GHSA-75h4-c557-j89r
Published: 2026-04-16

References

Related advisories

CVE-2026-41228 — critical · Packagist/froxlor/froxlor
CVE-2026-41229 — critical · Packagist/froxlor/froxlor
CVE-2026-26279 — critical · Packagist/froxlor/froxlor
CVE-2024-34070 — critical · Packagist/froxlor/froxlor
CVE-2026-52793 — high · Packagist/froxlor/froxlor
CVE-2026-41234 — high · Packagist/froxlor/froxlor
CVE-2026-41237 — high · Packagist/froxlor/froxlor
CVE-2026-41236 — high · Packagist/froxlor/froxlor

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.