CVE-2026-1480: Quatuor Evaluación de Desempeño (EDD) · SQL Injection
Affects Quatuor Evaluación de Desempeño (EDD)Source CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| QuatuorEvaluación de Desempeño (EDD) | Affected
| Fixed in– |
AI-suggested
1. Implement immediate input validation and sanitization on the 'Id_usuario' parameter to reject or properly escape special SQL characters. 2. Refactor database access code to use parameterized queries or prepared statements, eliminating direct concatenation of user input into SQL commands. 3. Deploy Web Application Firewalls (WAFs) configured to detect and block SQL injection patterns, especially those targeting the vulnerable endpoint. 4. Monitor outbound network traffic for unusual connections or data flows indicative of out-of-band data exfiltration attempts, using network intrusion detection systems (NIDS). 5. Conduct thorough code reviews and security testing (including dynamic and static analysis) to identify and remediate similar injection points. 6. Engage with the vendor or development team to obtain patches or updates as soon as they become available. 7. Restrict database permissions to the minimum necessary, limiting the potential impact of any injection exploit. 8. Educate developers and administrators on secure coding practices and the risks of SQL injection vulnerabilities. 9. Consider network segmentation to isolate critical systems and reduce the attack surface. 10. Prepare incident response plans specifically addressing OOB SQL injection scenarios to enable rapid containment and remediation.
Description
An out-of-band SQL injection vulnerability (OOB SQLi) has been detected in the Performance Evaluation (EDD) application developed by Gabinete Técnico de Programación. Exploiting this vulnerability in the parameter 'Id_usuario' in '/evaluacion_objetivos_anyo_sig_evalua.aspx', could allow an attacker to extract sensitive information from the database through external channels, without the affected application returning the data directly, compromising the confidentiality of the stored information.