# CVE-2026-30082: Cross-site scripting in n/a

> Attackers can execute arbitrary scripts via stored XSS in the Software Package List edit feature of IngEstate Server.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-xm7v-wmqf-6g4f

## What is CVE-2026-30082?

CVE-2026-30082 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple stored cross-site scripting (XSS) vulnerabilities in the Edit feature of the Software Package List page of IngEstate Server v11.14.0 allow attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the About application, What's news, or Release note parameters.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-30082 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30082 exists.

Public exploit code:

- Stored cross-site scripting (XSS) vulnerabilities in IngEstate Server v11.14.0 (github_poc): https://github.com/Cr0wld3r/CVE-2026-30082

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30082 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30082 exists.

Affected product: n/a. 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-30082/ (Markdown: https://insights.sbomify.com/CVE-2026-30082/index.md)
```

## Sources

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

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