CVE-2025-1557 Overview
CVE-2025-1557 is a Cross-Site Request Forgery (CSRF) vulnerability in OFCMS version 1.1.3, an open-source content management system. The flaw resides in an unspecified function of the application and allows remote attackers to trick authenticated users into submitting unwanted requests to the application. The exploit details have been publicly disclosed, increasing the risk of opportunistic abuse. The weakness is tracked under CWE-352: Cross-Site Request Forgery and requires user interaction to succeed.
Critical Impact
Attackers can perform unauthorized state-changing actions in OFCMS on behalf of an authenticated user by luring them to a malicious page.
Affected Products
- OFCMS version 1.1.3
- ofcms_project OFCMS web application
- Deployments exposing the OFCMS administrative interface to browsers with active sessions
Discovery Timeline
- 2025-02-22 - CVE-2025-1557 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-1557
Vulnerability Analysis
CVE-2025-1557 affects OFCMS 1.1.3, a Java-based open-source CMS. The application fails to validate the authenticity of state-changing HTTP requests, allowing an attacker-controlled site to submit forged requests through a victim's authenticated browser session. Because OFCMS does not enforce anti-CSRF tokens or verify request origin on the affected endpoint, requests inherit the victim's privileges.
The attack is network-reachable and requires user interaction, typically by convincing the victim to visit a crafted page or click a malicious link. Successful exploitation can modify application state, such as altering configuration data or creating unauthorized content, depending on the victim's role.
Root Cause
The root cause is missing CSRF protection on sensitive endpoints in OFCMS 1.1.3, as classified under CWE-352. The application does not require an unpredictable token tied to the user's session for state-changing operations. It also lacks strict validation of the Origin or Referer headers, so requests originating from third-party domains are processed as legitimate.
Attack Vector
Exploitation follows the standard CSRF pattern. The attacker hosts a webpage containing an auto-submitting HTML form or a scripted fetch call targeting an OFCMS endpoint. When a logged-in OFCMS user visits the page, the browser automatically attaches session cookies to the outbound request. The OFCMS server processes the action as if the victim initiated it.
Further technical details are available in the Yuque CSRF Vulnerability Analysis and the VulDB entry #296508.
Detection Methods for CVE-2025-1557
Indicators of Compromise
- Inbound POST or GET requests to OFCMS administrative endpoints containing an external Referer or Origin header
- Sudden creation, modification, or deletion of OFCMS content, users, or configuration entries without corresponding admin console activity
- Unexpected HTTP requests from authenticated OFCMS sessions immediately after users visit external URLs
Detection Strategies
- Review OFCMS access logs for state-changing requests where the Referer header does not match the OFCMS host
- Correlate web server logs with user browsing telemetry to identify session-riding patterns
- Deploy a web application firewall (WAF) rule that flags cross-origin POST requests to /admin or content management endpoints
Monitoring Recommendations
- Enable audit logging in OFCMS for all administrative and content-modification actions
- Forward OFCMS logs to a centralized SIEM to alert on anomalous cross-origin activity
- Monitor for repeated failed CSRF exploitation attempts as a precursor to targeted campaigns
How to Mitigate CVE-2025-1557
Immediate Actions Required
- Restrict access to the OFCMS administrative interface to trusted networks or VPN-only ranges
- Instruct administrators to log out of OFCMS when not actively using it to shorten session lifetimes
- Deploy a WAF rule blocking state-changing requests without a same-origin Referer header
Patch Information
No vendor patch is currently referenced in the NVD entry for CVE-2025-1557. Monitor the ofcms_project repository and vendor channels for an official update to OFCMS beyond version 1.1.3.
Workarounds
- Configure the application server to set the SameSite=Strict attribute on OFCMS session cookies to block cross-site cookie transmission
- Add a reverse proxy layer that rejects requests to OFCMS endpoints when the Origin header does not match the application host
- Require administrators to use a dedicated browser profile isolated from general web browsing while managing OFCMS
# Example Nginx snippet enforcing same-origin for OFCMS state-changing requests
location /ofcms/ {
if ($request_method = POST) {
set $csrf_block "1";
if ($http_origin = "https://ofcms.example.com") {
set $csrf_block "0";
}
if ($csrf_block = "1") {
return 403;
}
}
proxy_pass http://ofcms_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

