Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged user
-
ExploitManipulate 'ids' parameter in AmCharts Data API request
-
ImpactRead unauthorized chart/time-series data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires a valid authenticated low-privileged account on the Scada-LTS 2.8.0 web application (PR:L) and network reachability to the AmCharts Data API endpoint; the attacker then manipulates the 'ids' argument processed by HttpServletRequest.getParameter in AmChartValuesAPI.java to reference identifiers outside their authorization scope. Limiting factors: exploitation is not possible fully unauthenticated (an account/session is needed), no user interaction is required of a victim, and impact is confined to unauthorized reading of data (confidentiality, low) with no integrity or availability consequences. The source evidence does not describe any non-default configuration prerequisite, so the flaw appears to affect the standard deployment of this version. |
| Impact | All signals point to this being a low-priority issue rather than an urgent one. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N) yields a base score of 2.1, driven by the fact that only confidentiality is affected and only at a low level (VC:L), with no integrity or availability impact. The vector is network-reachable with low attack complexity and no user interaction, but it requires an authenticated low-privileged account (PR:L), which meaningfully limits exposure. SSVC/temporal signal E:P indicates a Proof-of-Concept maturity, consistent with the description's statement that 'the exploit has been published,' but this is PoC-grade evidence, not confirmed active exploitation. The vuln.today decision label is 'monitor' - the lowest actionable tier - and the CVE is NOT listed in CISA KEV. No EPSS score was provided in the input, so exploitation probability cannot be quantified here. The CWE-639 classification (authorization bypass through a user-controlled key, i.e. an IDOR on the 'ids' argument) matches the described behavior. Net assessment: a genuine but low-severity authorization/IDOR flaw whose real-world risk is bounded by the authentication requirement, the confidentiality-only impact, and the niche deployment base of Scada-LTS; it warrants patching on a normal cycle rather than emergency action. |
| Exploit ScenarioDerived | An attacker holding a valid low-privileged Scada-LTS account sends a crafted request to the AmCharts Data API, tampering with the 'ids' parameter handled by HttpServletRequest.getParameter in AmChartValuesAPI.java to reference data series they are not authorized to view. Because the endpoint does not properly check the caller's authorization against the requested identifiers, it returns time-series/chart data belonging to other users or resources. A public exploit has reportedly been published per VulDB, and the low attack complexity (AC:L, no user interaction) makes the request trivial to reproduce once authenticated. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 24, 2026
Authorization bypass in Scada-LTS 2.8.0 lets a low-privileged authenticated user read data outside their assigned scope by tampering with the 'ids' parameter handled by HttpServletRequest.getParameter in AmChartValuesAPI.java (the AmCharts Data API). Only confidentiality is affected and only at a low level, with no integrity or availability impact and no victim interaction required; the attacker must already hold a valid account on the web application and be able to reach the API endpoint. The vendor acknowledges the issue and states a security-hardened release is in preparation, while a published exploit is referenced and the CVSS 4.0 vector carries E:P; CISA KEV does not list this CVE and the priority label is monitor, so no confirmed active exploitation is established.
RemediationAI
No vendor-released patch has been identified at time of analysis: the vendor's stated position is that a new release with security enhancements is in preparation and will be introduced to the community soon, with no fix version, commit or advisory link supplied in the references. Until that release is available, the compensating controls that follow from the described attack path are to enforce server-side object-level authorization on the 'ids' value in AmChartValuesAPI.java so that identifiers outside the session's scope are rejected rather than resolved (a code change local to the handler, requiring a rebuilt or patched deployment and regression testing of chart rendering), and to limit who can reach the AmCharts Data API endpoint at all by restricting network access to it and reducing the number of accounts holding even low-privileged logins (trade-off: legitimate dashboards and integrations that call the endpoint from outside the permitted network range or from shared accounts will break). Monitoring of API requests for identifiers outside a user's normal set can surface probing but does not prevent the disclosure; only the authorization check or the vendor's forthcoming release addresses the root cause. Track https://vuldb.com/vuln/425987 for updates.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Scada-LTS is an open-source Java-based SCADA/HMI platform, and the affected component is its AmCharts Data API, which supplies time-series values to chart widgets. The root cause class is CWE-639, Authorization Bypass Through User-Controlled Key: AmChartValuesAPI.java reads the 'ids' argument through HttpServletRequest.getParameter and uses that client-supplied value to select the data points to return, without verifying that the requesting session is entitled to the referenced identifiers. Because the parameter is a raw request value, any authenticated user can substitute identifiers belonging to other data points or tenants and receive their values in the response. The weakness is an object-level (per-record) authorization gap rather than a missing login check, so the CVSS 3.1 assessment keeps the attack vector network-based with PR:L and confines impact to C:L with I:N/A:N. CPE data records only cpe:2.3:a:n/a:scada-lts:*:*:*:*:*:*:*:*, i.e. the product is identified but the vendor field and version granularity are not captured, so the exact affected build range rests on the reported 2.8.0; the sources do not describe how the flow behaves in non-default deployments, and that remains unverified.
Know when Java gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Network-reachable IDOR requiring a low-privileged authenticated account (PR:L), trivial to trigger (AC:L), exposing only limited data (C:L) with no integrity or availability impact.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
2DescriptionCVE.org
A flaw has been found in Scada-LTS 2.8.0. Affected by this vulnerability is the function HttpServletRequest.getParameter of the file AmChartValuesAPI.java of the component AmCharts Data API. Executing a manipulation of the argument ids can lead to authorization bypass. The attack can be executed remotely. The exploit has been published and may be used. The vendor announces: "At this moment we are working on new release with security enhancements which will be introduced to the community soon."
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
EUVD-2026-109243
GHSA-jcmm-wjpq-hq39
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB