CVE-2025-55797
BaseFortify
Publication date: 2025-09-30
Last updated on: 2025-10-07
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| formcms | formcms | 0.5.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an improper access control issue in FormCms version 0.5.4. It occurs in the /api/schemas/history/[schemaId] endpoint, where unauthenticated attackers can access historical schema data if they know or can guess a valid schemaId. Essentially, the system does not properly restrict access to this endpoint, allowing unauthorized users to retrieve potentially sensitive historical schema information without authentication.
How can this vulnerability impact me? :
This vulnerability can impact you by exposing historical schema data to unauthorized users. If an attacker knows or guesses a valid schemaId, they can access past versions of your data schemas without needing to authenticate. This could lead to leakage of sensitive or proprietary information about your data structure, potentially aiding further attacks or data misuse.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring HTTP requests to the /api/schemas/history/[schemaId] endpoint for unauthenticated access attempts. You can use network traffic analysis tools like curl or wget to test access without authentication by trying to retrieve historical schema data with known or guessed schemaId values. For example, a command like `curl -v http://<host>/api/schemas/history/<schemaId>` can be used to check if the endpoint returns data without authentication. Additionally, inspecting web server logs for unauthenticated GET requests to this endpoint may help identify exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the /api/schemas/history/[schemaId] endpoint by enforcing proper authentication and authorization checks to prevent unauthenticated users from accessing historical schema data. Applying access control rules in the API to ensure only authorized users can retrieve schema history is critical. If possible, update FormCMS to a patched version that addresses this vulnerability. Additionally, monitor and block suspicious requests to this endpoint at the network or application firewall level until a fix is applied. [1, 2]