OPEXUS FOIAXpress CVE-2025-61997
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as administrative user
-
DeliveryUpload malicious payload via banner image field
-
ExploitStore XSS in Annual Report template
-
ExecutionVictim generates Annual Report triggering script
-
ImpactSteal session cookies and sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with administrative privileges (PR:H) that has access to the Annual Report Enterprise Banner image upload field - this is the exact feature that fails to sanitize uploaded content. The payload does not execute at upload time; it fires only when a separate victim user performs the specific action of generating an Annual Report (UI:P/passive interaction), so exploitation depends on a second user exercising that reporting workflow. Limiting factors: the high administrative privilege barrier to plant the payload, the dependence on victim-initiated report generation, and the requirement that the target FOIAXpress instance be at a version before 11.13.3.0. These conditions make opportunistic or mass exploitation impractical; it is realistically an insider-abuse or post-admin-compromise scenario. |
| Impact | This is a genuinely low-to-moderate priority issue despite being a stored XSS, and the signals are consistent rather than conflicting. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:P) scores 4.8 (Medium), and the key limiting factor is PR:H - exploitation requires an already-authenticated ADMINISTRATIVE user to plant the payload, so this is a privileged-insider / post-compromise escalation vector, not a path for an external unauthenticated attacker. UI:P confirms a second condition: a victim must independently generate an Annual Report for the payload to fire. EPSS reinforces low real-world risk at 0.24% (14th percentile). There is no CISA KEV listing and no public exploit referenced, so exploitation status is 'no public exploit identified at time of analysis.' Impact is bounded (VC:L/VI:L/VA:L, SC:N) - it does not grant system compromise, only limited action-on-behalf-of a victim within the application. The main nuance to verify: the attack vector is rated AV:N, but because the attacker must be a logged-in admin of the FOIAXpress instance, the practical exposure is far narrower than 'network' implies - treat this as an authenticated stored-XSS with a high privilege barrier, not an internet-facing critical. |
| Exploit ScenarioDerived | A malicious or compromised FOIAXpress administrator uploads a crafted file to the Annual Report Enterprise Banner image upload field containing injected JavaScript instead of a legitimate image. When another user (e.g., a less-privileged staffer or reviewer) later generates an Annual Report, the stored script executes in their authenticated browser session, letting the attacker exfiltrate the victim's session cookies, credentials, or sensitive FOIA data. No public proof-of-concept exploit is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Stored cross-site scripting in OPEXUS FOIAXpress before 11.13.3.0 allows an authenticated administrative user to inject JavaScript or other content via the Annual Report Enterprise Banner image upload field, which then executes in the context of other users when they generate an Annual Report. Successful exploitation can let the attacker perform actions on behalf of the victim, including stealing session cookies, credentials, or sensitive data. Exploitation requires a high-privileged admin account to plant the payload and a separate victim user to trigger report generation; no public exploit code exists and EPSS is 0.24% (14th percentile), making this a low-to-moderate priority issue that is realistically an insider-abuse or post-admin-compromise scenario.
RemediationAI
Apply the vendor-released patch by upgrading to OPEXUS FOIAXpress 11.13.3.0 or later, as specified in the official release notes at https://docs.opexustech.com/docs/foiaxpress/11.13.0/FOIAXpress_Release_Notes_11.13.3.0.pdf. If immediate patching is not feasible, restrict access to the Annual Report Enterprise Banner image upload field to only the most trusted administrative personnel, since exploitation requires an authenticated account with administrative privileges (PR:H). Consider disabling or removing the image upload feature entirely if it is not business-critical, accepting the loss of Annual Report banner customization as a trade-off. Monitor administrative uploads for unexpected content such as files containing script tags or unusual MIME types, and enforce a policy that other users generate Annual Reports only after banner content has been verified as benign. These compensating controls reduce exposure but do not fully eliminate the stored XSS vector; patching remains the definitive fix. No alternative patch versions are identified in the available data.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a stored cross-site scripting (XSS) flaw classified as CWE-79 (Improper Neutralization of Input During Web Page Generation). The affected component is the Annual Report Enterprise Banner image upload field in OPEXUS FOIAXpress. Because the application fails to sanitize or validate uploaded content, an administrative user can embed JavaScript or other active content within an image file or upload metadata. This content is stored and later rendered without proper encoding when other users generate an Annual Report, causing execution in their browser session. The CPE string cpe:2.3:a:opexustech:foiaxpress:*:*:*:*:*:*:*:* identifies the product line, and all versions before 11.13.3.0 are presumed affected. The original CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N) yields a base score of 4.8, while an independent CVSS 3.1 assessment (AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N) confirms low confidentiality and integrity impact with scope change, driven by the requirement for high administrative privileges and victim interaction. The primary mitigating factors are the high privilege barrier to plant the payload and the dependence on a second user performing the specific report-generation action.
Know when Foiaxpress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Admin-only payload placement forces PR:H; victim must generate a report so UI:R; stored script runs in another user's context so S:C with limited C:L/I:L and no availability impact.
Primary rating from Vendor (9119a7d8-5eab-497f-8521-727c672e3725).
CVSS VectorVendor: 9119a7d8-5eab-497f-8521-727c672e3725
DescriptionCVE.org
OPEXUS FOIAXpress before 11.13.3.0 allows an administrative user to inject JavaScript or other content within the Annual Report Enterprise Banner image upload field. Injected content is 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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
More in Foiaxpress
View allRemote unauthenticated attackers can reset the administrator password in OPEXUS FOIAXpress versions prior to 11.13.2.0,
Stored cross-site scripting in OPEXUS FOIAXpress before 11.13.3.0 lets an authenticated administrative user upload an SV
Stored cross-site scripting in OPEXUS FOIAXpress before 11.13.3.0 allows an authenticated administrative user to place J
Stored cross-site scripting (CWE-79) in OPEXUS FOIAXpress before 11.13.3.0 lets an actor who already holds administrativ
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB