N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-55797

CVE-2025-55797: FormCMS has an improper access control vulnerability in the /api/schemas/history/[schemaId] endpoint

An improper access control vulnerability in FormCms v0.5.4 in the /api/schemas/history/[schemaId] endpoint allows unauthenticated attackers to access historical schema data if a valid schemaId is known or guessed.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-55797

CVE-2025-55797:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
FormCMS	nuget	<= 0.5.4	0.5.5

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability described is an improper access control issue in the /api/schemas/history/[schemaId] endpoint of FormCMS, allowing unauthenticated access to schema history. The analysis started by investigating the provided GitHub issue, but it did not contain direct commit links. The next step was to compare the git tags for the last vulnerable version (v0.5.4) and the first patched version (v0.5.5). This comparison revealed a commit 8d1851bee044423fb83eb9e636626b3003fe36c9 with the message "fix schema history security issue", confirming it as the security patch.

Analysis of this commit's changes showed that the History method in server/FormCMS/Cms/Services/SchemaService.cs was modified. Previously, the function fetched and returned data directly. The patch introduced a call to a new hook, hook.SchemaPostGetHistory.Trigger(...), before returning the data. This hook is used to implement the missing access control check. The vulnerable function is FormCMS.Cms.Services.SchemaService.History because it was the function that lacked the necessary security controls, and its modification was the direct fix for the vulnerability. During exploitation, this function would be on the call stack as it processes the malicious request.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.