Stored XSS via unsanitized illness name
Published Jul 16, 2025 · Updated Jul 18, 2025
Stored XSS in WeGIA before 3.4.5 allows remote attackers to run scripts in users' browsers through a crafted nome value. The adicionar_enfermidade.php endpoint accepts the nome POST parameter without adequate validation or sanitization, stores the value, and later emits it into an affected page. Exploitation requires a user to open that page; the script then runs in the site's origin and can read session data or act through the victim's session.
Summary
What happened
Stored XSS in WeGIA before 3.4.5 allows remote attackers to run scripts in users' browsers through a crafted nome value. The adicionar_enfermidade.php endpoint accepts the nome POST parameter without adequate validation or sanitization, stores the value, and later emits it into an affected page. Exploitation requires a user to open that page; the script then runs in the site's origin and can read session data or act through the victim's session.
The record
- CVE
- CVE-2025-53933
- Published
- Jul 16, 2025
- Updated
- Jul 18, 2025
- Vendor
- LabReDeS - Laboratório de Redes, Desenvolvimento e Segurança
- Product
- WeGIA
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2025CVE publishedPublication date reported by the CVE source.
- Jul 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.4.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory script-alert proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo