Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS 5.1 score reflects moderate risk with specific mitigating factors. The vector indicates network-based attack vector (AV:N), low complexity (AC:L), no privilege requirements (PR:N), and user interaction required (UI:A), meaning victims must click a malicious link. The scope is limited (SC:L), and impact is confined to session integrity and availability with no confidentiality breach (VC:N, VI:N, VA:N). CISA's SSVC framework indicates no confirmed exploitation, non-automatable delivery (requires user click), and only partial technical impact. Critically, no active exploitation (KEV status) and no public POC have been reported, significantly reducing real-world urgency compared to the raw CVSS score. Organizations should prioritize patching based on GDTaller's prominence in their environment and user exposure to untrusted links, rather than treating this as a critical incident. |
| Exploit ScenarioDerived | An attacker crafts a malicious URL with JavaScript payload embedded in the 'site' parameter (e.g., app_login.php?site=<script>alert('XSS')</script> or site=javascript:fetch(...)) and sends it to a GDTaller user via phishing email, social engineering, or posting on forums. When the victim clicks the link while authenticated or considering logging in, the browser executes the attacker's script in the context of the GDTaller domain, potentially allowing session hijacking, credential theft, or malware injection. Because user interaction (clicking) is required and the attack is non-automatable, the real-world exploitation rate remains low despite network accessibility. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
GDTaller is vulnerable to reflected cross-site scripting (XSS) in the app_login.php file, specifically through the 'site' parameter, allowing unauthenticated remote attackers to execute arbitrary JavaScript in victim browsers via malicious URLs. The vulnerability affects GDTaller versions prior to an unspecified patch release and carries a CVSS 5.1 score reflecting low immediate confidentiality impact but limited scope and user interaction requirement. A vendor patch is available from INCIBE, though no public exploit code has been identified at time of analysis.
RemediationAI
Upgrade GDTaller to the patched version released by the vendor via INCIBE's security advisory. The patch is confirmed available per vendor notification. Until patching is completed, implement input validation and output encoding mitigations: enforce strict Content Security Policy (CSP) headers to prevent inline script execution, apply HTML entity encoding to all user-supplied input reflected in responses, and consider deploying a Web Application Firewall (WAF) with XSS signature rules to block malicious payloads in the 'site' parameter. Additionally, educate end users to avoid clicking links from untrusted sources, and monitor access logs for suspicious 'site' parameter values containing script tags or JavaScript protocols. Consult https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-gdtaller for exact patched version numbers and deployment instructions.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability is a classic reflected XSS flaw (CWE-79) in PHP-based web application input handling. The app_login.php endpoint fails to properly sanitize or encode user-supplied input in the 'site' parameter before reflecting it back to the client in HTTP responses. GDTaller (cpe:2.3:a:gdtaller:gdtaller) is a PHP web application, and the lack of context-appropriate output encoding allows attacker-controlled script payloads to be parsed and executed by the victim's browser within the security context of the vulnerable domain. Reflected XSS differs from stored XSS in that the payload must be delivered in the request itself; the server does not persistently store it.
Know when Gdtaller gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
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 en 'site' parameter in 'app_login.php'.
Executive ViewAI
CVE-2025-41026 presents moderate security risk, a cross-site scripting vulnerability rated CVSS 5.1. Attackers could inject scripts to steal sessions or perform actions as authenticated users. A patch is available and should be applied during regular vulnerability management.
Apply vendor patch. If patching is delayed: implement CSP headers, enable HttpOnly cookies, deploy WAF XSS rules.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2025-209047
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB