CVE-2025-22509
Critical PHP LFI in TMRW-studio Atlas <=2.1.0
Is CVE-2025-22509 being exploited?
Not confirmed. CVE-2025-22509 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.58% probability of exploitation in the next 30 days.
How severe is CVE-2025-22509?
CVE-2025-22509 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-22509?
Not known from our data. No patch reference has been recorded for CVE-2025-22509, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2025-22509 affect?
CVE-2025-22509 affects TMRW-studio Atlas <=2.1.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-22509?
Monitor vendor patch; validate include paths and sanitize inputs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
LFI allows reading server files and may enable code execution via crafted includes
Patch when possible
- affected<= 2.1.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.