CVE-2024-7901
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 · uneditedA vulnerability has been found in Scada-LTS 2.7.8 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /Scada-LTS/app.shtm#/alarms/Scada of the component Message Handler. The manipulation leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. NOTE: A fix is planned for the upcoming release at the end of September 2024.
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 confidenceCross-site scripting (XSS) vulnerability in Scada-LTS 2.7.8 Message Handler component at the /Scada-LTS/app.shtm#/alarms/Scada endpoint. The vulnerability allows injection of malicious scripts through manipulated input, potentially compromising user sessions or delivering malicious content to other users.
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= 2.7.8CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 Scada-LTS installation versionCheck the application's version information, typically found in the WAR file name, deployment descriptor, or within the application UI (often in About or System Info sections). Check for files like version.properties, MANIFEST.MF, or the pom.xml in the web root.Affected if The installed version is exactly 2.7.8
-
Confirm Message Handler component is activeVerify that the Message Handler module is deployed and enabled in the Scada-LTS installation. Check the web application's configuration files and loaded modules.Affected if Message Handler component is present and enabled in the application
-
Verify alarm interface endpoint accessibilityAccess or scan for the /Scada-LTS/app.shtm#/alarms/Scada endpoint to confirm it is exposed. Check web server configuration and application routing.Affected if The /Scada-LTS/app.shtm#/alarms/Scada endpoint is accessible and responds to requests
-
Inspect alarm message input handlingExamine how the Message Handler processes input in the alarm interface. Review the application's handling of user-supplied data in alarm creation or modification functions.Affected if User-provided messages can be submitted to the alarm system without context-aware sanitization or output encoding
The environment is affected if Scada-LTS version 2.7.8 is running with the Message Handler component enabled and the /Scada-LTS/app.shtm#/alarms/Scada endpoint is accessible without proper input validation on message fields.
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 robust input validation and output encoding on the Message Handler component. Apply context-aware sanitization for all user-supplied data before rendering in the alarm interface. A WAF can serve as an interim control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7901 — 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-2024-7901 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