Threats / Srimax / CVE-2025-27920
CVE-2025-27920
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Srimax Output Messenger vulnerability
Srimax Output Messenger contains a directory traversal vulnerability (CWE-22) allowing attackers to access sensitive files outside intended directories, potentially exposing configuration data and arbitrary files.
Verdict
Today item — known-exploited.
A path traversal flaw in Output Messenger enables unauthenticated or low-privileged attackers to read sensitive files by manipulating file paths. Active exploitation in the wild increases risk. Patch immediately.
CISA KEV Yes · 2025-05-195EPSS 0.01775 (verify live)6CVSS 7.23CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-19).
Probability (EPSS)
EPSS 0.01775 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) · Affected: Srimax, Output Messenger. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-24 CWE-24 — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 14 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request with directory traversal sequences to escape the application's intended file directory.
Business
Sensitive configuration files, credentials, or application secrets become accessible to unauthorized parties.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I read exposed configuration files to identify further attack vectors or extract authentication tokens.
Business
Lateral movement and privilege escalation risks increase; attackers gain footholds for deeper compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I access system files or application data to understand the infrastructure and identify high-value targets.
Business
Operational security is compromised; attackers gain intelligence for targeted follow-up attacks.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05