CVE-2026-8604
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 · uneditedIn ScadaBR version 1.2.0, a CSRF vulnerability could allow an attacker to trigger any authenticated action through a victim's session by luring any logged-in user to a malicious webpage.
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 · high confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in ScadaBR version 1.2.0. The application lacks proper anti-CSRF tokens or origin validation, allowing attackers to craft malicious web pages that silently trigger authenticated actions on behalf of any logged-in user. Since the attacker can trigger 'any authenticated action,' all state-changing operations (configuration changes, device controls, user management) are vulnerable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify ScadaBR versionAccess the application's About or System Information page (typically found in the administrator settings or footer), or check the WAR file/version file deployed on the serverAffected if Version is 1.2 (specifically Scadabr 1.2)
-
Inspect login and authentication forms for CSRF tokensView the HTML source of login and authenticated pages (right-click > View Page Source), then search for hidden input fields with names like 'csrf', 'token', or similar anti-CSRF mechanismsAffected if No hidden CSRF token fields are present in authenticated form HTML
-
Check session cookie attributesOpen browser developer tools (F12), go to Application/Storage tab, examine the JSESSIONID or session cookie for SameSite and Secure attributesAffected if SameSite attribute is missing or set to None without Secure flag
-
Verify form action endpoints lack Origin/Referer validationReview HTTP requests sent when submitting state-changing forms (configuration changes, user management) using the Network tab - check if the server rejects requests with missing or mismatched Origin/Referer headersAffected if Server accepts form submissions without validating Origin/Referer headers
User is affected if running ScadaBR 1.2 AND authenticated action endpoints do not include hidden CSRF token fields in their HTML forms.
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 for all state-changing requests and validate the Origin or Referer header on sensitive operations. Alternatively, configure SameSite attribute on session cookies to 'Strict' or 'Lax'.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8604 — 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-2026-8604 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