Arbitrary code execution via template injection
Published Feb 21, 2025 · Updated Mar 3, 2025
Server-side template injection in MRCMS 3.1.2 allows attackers to execute arbitrary code through a crafted request payload. The disclosure identifies DispatcherServlet.java as the vulnerable locus but leaves the template engine, input parameter, and unsafe evaluation operation undisclosed. Attackers must reach the service from an adjacent network; no credentials or user interaction are required, and successful exploitation runs code in the application context.
Summary
What happened
Server-side template injection in MRCMS 3.1.2 allows attackers to execute arbitrary code through a crafted request payload. The disclosure identifies DispatcherServlet.java as the vulnerable locus but leaves the template engine, input parameter, and unsafe evaluation operation undisclosed. Attackers must reach the service from an adjacent network; no credentials or user interaction are required, and successful exploitation runs code in the application context.
The record
- CVE
- CVE-2025-25768
- Published
- Feb 21, 2025
- Updated
- Mar 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1190
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- MRCMS SSTI disclosure and proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo