dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-30082

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
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.

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 · high confidence

Stored cross-site scripting (XSS) vulnerabilities exist in the Edit feature of the Software Package List page of IngEstate Server v11.14.0. Attackers can inject malicious scripts into three parameters (About application, What's news, and Release note) that are persisted and executed when other users view the affected content.

MitigationImplement strict input validation and context-appropriate output encoding for the About application, What's news, and Release note parameters. Consider adding Content Security Policy headers as defense-in-depth.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IngEstate Server installation and version
    Locate the IngEstate Server installation directory or check the product's about/version panel. Common locations include the installation root folder or the administration console. Verify the exact version number.
    Affected if The installed version is IngEstate Server v11.14.0 exactly, or any version within the v11.14.x minor release line if the vendor confirms backport status.
  2. Access the Software Package List page
    Navigate to the Software Package List page within the IngEstate Server web interface. This is typically found under the administration or package management section of the application.
    Affected if The page is accessible without authentication bypass, indicating the feature is enabled in the environment.
  3. Locate the Edit feature for the affected parameters
    Locate the Edit button or form on the Software Package List page that allows modification of the three parameters: About application, What's news, and Release note.
    Affected if The Edit feature is present and allows input into any of the three affected parameters.
  4. Inspect current values of the three parameters
    View the Software Package List page source or use browser developer tools to inspect the HTML rendering of the About application, What's news, and Release note fields. Check if the values are rendered with proper encoding.
    Affected if The parameters contain unsanitized HTML or JavaScript content, or the output rendering shows no visible encoding (e.g., raw display of script tags or event handlers).
  5. Verify input validation is not applied
    Attempt to input a benign test string containing special characters (< > " ') into each of the three parameters via the Edit feature, then view the output to see if characters are preserved as-is or escaped.
    Affected if Special characters are stored and rendered without HTML entity encoding, indicating input validation is not implemented.

A user is affected if they are running IngEstate Server v11.14.0 (or an affected variant) and the Software Package List Edit feature with its About application, What's news, or Release note parameters is accessible and renders user-supplied content without proper output encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and context-appropriate output encoding for the About application, What's news, and Release note parameters. Consider adding Content Security Policy headers as defense-in-depth.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30082 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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