CVE-2025-6512
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 · uneditedOn a client with a non-admin user, a script can be integrated into a report. The reports could later be executed on the BRAIN2 server with administrator rights.
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 script injection vulnerability in BRAIN2 allows a non-administrative client user to embed arbitrary script code into a report. When the report is later executed on the BRAIN2 server, the script runs with administrator-level privileges, enabling privilege escalation and potential full system compromise.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 installed BRAIN2 versionLocate the BRAIN2 installation directory and check version file, or run 'brain2 --version' or 'brain2 -v' command from the installation pathAffected if The installed version falls within the affected range (if known) or is any version prior to patch
-
Verify report creation permissions for non-admin usersLog in as a non-administrative user account and attempt to access the report creation or editing functionality in the BRAIN2 web interface or client applicationAffected if Non-administrative users have the ability to create, modify, or save reports in the system
-
Inspect report file contents for script execution capabilityExamine the report file format (typically .br2, .xml, or similar) stored in the reports directory and check if the system permits embedding of script or code execution statements within report definitionsAffected if The report format allows embedding of script code, macros, or executable content that could be parsed and run by the server
-
Check report execution privilege contextReview server logs or configuration to determine under which user context reports are executed on the BRAIN2 server; examine if reports run with elevated administrator-level privileges rather than the authenticated user's privilegesAffected if Reports execute with administrator-level or elevated privileges rather than the privileges of the user who created or triggered the report
You are affected if non-administrative users can embed script code into reports that then execute with administrator-level privileges on the BRAIN2 server.
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 strict input validation and sanitization for all report content to prevent script injection. Enforce least-privilege principles by ensuring reports execute with the privileges of the authenticated user rather than elevated admin rights.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6512 — 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-6512 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