# CVE-2025-41026: Multiple vulnerabilities in GDTaller

> Reflected XSS in GDTaller allows attackers to execute JavaScript in victims' browsers via a malicious URL in the site parameter.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-f5f8-fq88-qvf9

## What is CVE-2025-41026?

CVE-2025-41026 is a medium-severity cross-site scripting vulnerability in GDTaller, published on 26 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

Reflected Cross Site Scripting (XSS) vulnerabilities in GDTaller. These vulnerabilities allows an attacker execute JavaScript code in the victim's browser  by sending a malicious URL in 'site' parameter in 'app_login.php'.

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

## Which versions are affected by CVE-2025-41026?

It affects 1 product.


Products: Gdtaller Gdtaller.

## How do I fix CVE-2025-41026?

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

## Is CVE-2025-41026 being exploited?

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

## Other vulnerabilities in GDTaller

- [CVE-2025-41027](https://insights.sbomify.com/CVE-2025-41027/): Multiple vulnerabilities in GDTaller (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41026 and fix it if it is affected.

What it is: CVE-2025-41026 is a medium-severity cross-site scripting vulnerability in GDTaller, published on 26 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: There is no known exploitation of CVE-2025-41026 in the wild and no public exploit code.

Affected product: GDTaller. 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-2025-41026/ (Markdown: https://insights.sbomify.com/CVE-2025-41026/index.md)
```

## Sources

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

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