How severe is CVE-2018-20663?

CVE-2018-20663 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-20663?

CVE-2018-20663 affects the following packages: com.haulmont.cuba:cuba-web-toolkit (Maven), com.haulmont.cuba:cuba-web-toolkit (Maven), com.haulmont.cuba:cuba-web-toolkit (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-20663?

Update com.haulmont.cuba:cuba-web-toolkit to 6.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-20663 is resolved across your whole dependency graph.

How do I detect CVE-2018-20663 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.haulmont.cuba:cuba-web-toolkit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-20663 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2018-20663 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-20663, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-20663?

CVE-2018-20663 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-20663?

CVE-2018-20663 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-20663 published, and has it been updated?

CVE-2018-20663 was published on January 3, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2018-20663 — cuba-web-toolkit

MEDIUMFix: cuba-platform/cuba@be6aa41

CVE-2018-20663 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in com.haulmont.cuba:cuba-web-toolkit. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.haulmont.cuba:cuba-web-toolkit — see the affected versions and patch details below.

The Reporting Addon for CUBA Platform has Persistent XSS

Also known asGHSA-rff7-964g-pppx

Published

Jan 3, 2019

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕com.haulmont.cuba:cuba-web-toolkit☕com.haulmont.cuba:cuba-web-toolkit☕com.haulmont.cuba:cuba-web-toolkit

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The Reporting Addon (aka Reports Addon) through 2019-01-02 for CUBA Platform through 6.10.x has Persistent XSS via the "Reports > Reports" name field.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.haulmont.cuba:cuba-web-toolkit`	≥ 6.10.0&&< 6.10.7	6.10.7`com.haulmont.cuba:cuba-web-toolkit:6.10.7`
☕Maven	`com.haulmont.cuba:cuba-web-toolkit`	≥ 6.9.0&&< 6.9.8	6.9.8`com.haulmont.cuba:cuba-web-toolkit:6.9.8`
☕Maven	`com.haulmont.cuba:cuba-web-toolkit`	all versions	6.8.15`com.haulmont.cuba:cuba-web-toolkit:6.8.15`

Affected Products

2 products · 2 configurations

Application

cuba platformhaulmont

≤ 6.10.7

range

Application

reportinghaulmont

≤ 2019-01-02

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Reporting Addon (aka Reports Addon) through 2019-01-02 for CUBA Plat…

github.comNVDJan 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.haulmont.cuba:cuba-web-toolkit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.haulmont.cuba:cuba-web-toolkit to 6.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-20663 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

The Reporting Addon (aka Reports Addon) through 2019-01-02 for CUBA Platform through 6.10.x has Persistent XSS via the "Reports > Reports" name field.

O3 Security · Impact-Aware SCA

Is CVE-2018-20663 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jan 3, 2019

First exploit

Jan 15, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2018-20663

GHSA-rff7-964g-pppx

References

Advisorynvd.nist.gov · CVE 2018 20663 Webgithub.com Webgithub.com · be6aa41ff36a365e2a995d37861e5acfcd32c2c5 Webgithub.com · e9f972beeae42dc6dbc3aaa6b6ecc9814c0eedb4 Webgithub.com · ec8784d8f596aa570604f4e5d5d4a7c3ae264c62 Packagegithub.com · reports Evidencegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-44267CVE-2026-96632CVE-2026-9086CVE-2026-118246CVE-2026-118251CVE-2026-118253CVE-2026-116797CVE-2026-118244Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026