What is the CVSS score of CVE-2025-28097?

CVE-2025-28097 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L. EPSS exploitation probability: 0.2%.

Which versions of Onenav are affected by CVE-2025-28097?

Organizations using OneNav 1.1.0 should be aware of moderate risk from CVE-2025-28097, a cross-site scripting vulnerability rated CVSS 5.5.

Is there a public PoC exploit available for CVE-2025-28097?

Yes, a public proof-of-concept exploit is available for CVE-2025-28097. Prioritise patching immediately. EPSS: 0.2%.

How to fix or mitigate CVE-2025-28097?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Verify Content-Security-Policy and output encoding.

Onenav CVE-2025-28097

MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2025-03-28 cve@mitre.org

XSS Onenav

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:33 vuln.today

PoC Detected

Apr 07, 2025 - 13:59 vuln.today

Public exploit code

CVE Published

Mar 28, 2025 - 22:15 nvd

MEDIUM 5.5

DescriptionCVE.org

OneNav 1.1.0 is vulnerable to Cross Site Scripting (XSS) in custom headers.

AnalysisAI

OneNav 1.1.0 is vulnerable to Cross Site Scripting (XSS) in custom headers. Rated medium severity (CVSS 5.5), this vulnerability is remotely exploitable. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. OneNav 1.1.0 is vulnerable to Cross Site Scripting (XSS) in custom headers. Affected products include: Onenav.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.