CVE-2025-30561
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Henrique Mouta CAS Maestro cas-maestro allows Stored XSS.This issue affects CAS Maestro: from n/a through <= 1.1.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Cross-Site Request Forgery (CSRF) vulnerability in CAS Maestro versions through 1.1.3 allows attackers to craft malicious requests that, when triggered by an authenticated user, result in stored Cross-Site Scripting (XSS). This occurs because the application lacks proper CSRF tokens or origin validation on state-changing operations, enabling attackers to inject persistent malicious scripts that execute in other users' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed CAS Maestro versionLocate the application version in the software itself, typically accessible via an admin panel, about page, or version file within the application root directory. Compare it against the affected range: versions through 1.1.3 (any version up to and including 1.1.3).Affected if The installed version is 1.1.3 or any earlier version of CAS Maestro.
-
Identify state-changing operationsReview the application for forms and API endpoints that perform state-changing actions such as creating, updating, or deleting user data, settings, or content. Common locations include user profile forms, content management interfaces, and configuration panels.Affected if The application contains forms or API endpoints that modify data without being restricted to read-only operations.
-
Inspect forms for CSRF token presenceExamine the HTML source of forms that perform state-changing operations. Look for hidden input fields containing anti-CSRF tokens, or JavaScript that adds token headers to form submissions. Check if each form includes a unique token value that changes per session or request.Affected if State-changing forms lack anti-CSRF token fields, or the tokens are missing from the form submission process.
-
Verify Origin or Referer header validationInspect the server-side code or proxy configuration that handles state-changing requests. Determine whether the application validates the Origin or Referer HTTP headers to verify the request originated from the legitimate domain.Affected if The application does not validate the Origin or Referer headers on state-changing endpoints, or such validation is absent entirely.
You are affected if you are running CAS Maestro version 1.1.3 or earlier AND your application lacks CSRF protection (missing tokens or Origin/Referer validation) on state-changing forms or API endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens on all state-changing operations (forms, API endpoints) and validate the Origin/Referer headers to prevent CSRF attacks that lead to stored XSS.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30561 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30561 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data