basicsecurity.net
Proof, not just disclosure.
Threats / Srimax / CVE-2025-27920
CVE-2025-27920 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-193EPSS 0.01812 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01812 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Srimax, Output Messenger. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-22 · Path TraversalPath traversal / file
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 7 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.