# CVE-2026-115803: Scada-LTS AmCharts Data API AmChartValuesAPI.java HttpServletRequest.getParameter authorization


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-jcmm-wjpq-hq39

## What is CVE-2026-115803?

CVE-2026-115803 is a medium-severity vulnerability in Scada-LTS, published on 24 Oct 2026. 

### Official description

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."

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-115803?


## How do I fix CVE-2026-115803?

No fix has been published for CVE-2026-115803 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115803 being exploited?

There is no known exploitation of CVE-2026-115803 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115803 and fix it if it is affected.

What it is: CVE-2026-115803 is a medium-severity vulnerability in Scada-LTS, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115803 in the wild and no public exploit code.

Affected product: Scada-LTS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115803/ (Markdown: https://insights.sbomify.com/CVE-2026-115803/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115803
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115803
- OSV: https://osv.dev/vulnerability/CVE-2026-115803

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115803/
Summaries are generated and may contain mistakes; the official description above is the record.