Skip to content
Web

CVE-2018-25408

8.7
High
EPSS 0.64%May 31, 2026

Unauthenticated path traversal in Open ISES Project 3.30A enables arbitrary file download.

common questions

Is CVE-2018-25408 being exploited?

Not confirmed. CVE-2018-25408 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.64% probability of exploitation in the next 30 days.

How severe is CVE-2018-25408?

CVE-2018-25408 is rated High with a CVSS score of 8.7. 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-2018-25408?

Not known from our data. No patch reference has been recorded for CVE-2018-25408, 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-2018-25408 affect?

CVE-2018-25408 affects Open ISES Project 3.30A. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2018-25408?

Patch when available; restrict download endpoint and validate filename inputs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Open ISES Project 3.30A
impact

Attacker can download config and system files via filename param, leading to data disclosure and potential further compromise.

action required

Immediate action required

affected versions
Openises Open ISES Project
  • affected3.30A

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free