CVE-2026-3024: Wakyma application web · Cross-site Scripting
Affects Wakyma application webSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WakymaWakyma application web | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-3024, organizations should implement multiple layers of defense: 1) Apply strict input validation and output encoding on all user-supplied data, especially in the vulnerable endpoint, to neutralize malicious scripts before storage or rendering. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3) Enforce the principle of least privilege by reviewing and limiting user permissions, particularly the ability to create personalized accounts or surveys. 4) Conduct regular security code reviews and penetration testing focused on XSS vulnerabilities. 5) Monitor application logs and user activity for suspicious behavior indicative of exploitation attempts. 6) If possible, isolate the vulnerable functionality or disable it temporarily until a vendor patch is released. 7) Educate users and administrators about the risks of XSS and safe usage practices. 8) Engage with the vendor for timely updates and patches addressing this vulnerability. These targeted actions go beyond generic advice by focusing on the specific vulnerable endpoint and user roles involved.
Description
Stored Cross-Site Scripting (XSS) vulnerability in the Wakyma web application, specifically in the endpoint 'vets.wakyma.com/configuracion/agenda/modelo-formulario-evento'. A user with permission to create personalized accounts could exploit this vulnerability simply by creating a malicious survey that would harm the entire veterinary team. At the same time, a user with low privileges could exploit this vulnerability to access unauthorized data and perform actions with elevated privileges.