# CVE-2024-10029: Eclipse GlassFish is vulnerable to Reflected XSS attacks through its Administration Console > Attackers can execute arbitrary scripts in the Eclipse GlassFish Administration Console via reflected cross-site scripting. - **Severity:** Medium 4.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:A/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 16 Jul 2025 - **Updated:** 16 Jul 2025 - **Also known as:** GHSA-vqrm-83g6-pfv4 ## What is CVE-2024-10029? CVE-2024-10029 is a medium-severity cross-site scripting vulnerability in Eclipse Glassfish, published on 16 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description In Eclipse GlassFish version 7.0.15 is possible to perform Reflected Cross-site scripting attacks in the Administration Console. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-10029? 4 open source packages ship an affected version, including org.glassfish.main.admingui:console-cluster-plugin and org.glassfish.main.admingui:console-common. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.glassfish.main.admingui:console-cluster-plugin` | Maven | All versions to 7.0.25 | None | | `org.glassfish.main.admingui:console-cluster-plugin` | Maven | All versions to 7.0.25 | None | | `org.glassfish.main.admingui:console-common` | Maven | All versions to 7.0.25 | None | | `org.glassfish.main.admingui:console-common` | Maven | All versions to 7.0.25 | None | Products: Eclipse Glassfish. ## How do I fix CVE-2024-10029? No fix has been published for CVE-2024-10029 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-10029 being exploited? There is no known exploitation of CVE-2024-10029 in the wild and no public exploit code. ## Other vulnerabilities in Eclipse Glassfish - [CVE-2026-12605](https://insights.sbomify.com/CVE-2026-12605/): Server-side request forgery in Eclipse GlassFish (critical 9.6) - [CVE-2026-2587](https://insights.sbomify.com/CVE-2026-2587/): GlassFish's gadget handler is vulnerable to RCE (critical 9.6) - [CVE-2026-2586](https://insights.sbomify.com/CVE-2026-2586/): GlassFish's Administration Console is Vulnerable to RCE (critical 9.1) - [CVE-2024-9408](https://insights.sbomify.com/CVE-2024-9408/): Eclipse GlassFish is vulnerable to Server Side Request Forgery attacks through specific endpoints (high 8.9) - [CVE-2024-9329](https://insights.sbomify.com/CVE-2024-9329/): Glassfish redirect to untrusted site (medium 6.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-10029 and fix it if it is affected. What it is: CVE-2024-10029 is a medium-severity cross-site scripting vulnerability in Eclipse Glassfish, published on 16 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-10029 in the wild and no public exploit code. Affected packages and fixed versions: - org.glassfish.main.admingui:console-cluster-plugin (Maven): affected all versions up to 7.0.25; no fix listed - org.glassfish.main.admingui:console-cluster-plugin (Maven): affected all versions up to 7.0.25; no fix listed - org.glassfish.main.admingui:console-common (Maven): affected all versions up to 7.0.25; no fix listed - org.glassfish.main.admingui:console-common (Maven): affected all versions up to 7.0.25; no fix listed 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-2024-10029/ (Markdown: https://insights.sbomify.com/CVE-2024-10029/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10029 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10029 - OSV: https://osv.dev/vulnerability/CVE-2024-10029 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-10029/ Summaries are generated and may contain mistakes; the official description above is the record.