Skip to main content
VulnerabilityPublished

CVE-2026-1482: Quatuor Evaluación de Desempeño (EDD) · SQL Injection

Affects Quatuor Evaluación de Desempeño (EDD)Source CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
QuatuorEvaluación de Desempeño (EDD)Affected
  • =All versions
Fixed in–

AI-suggested

  1. Immediate code remediation by developers to implement parameterized queries or prepared statements in the affected 'Id_evaluacion' parameter to prevent injection.
  2. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters interacting with the database.
  3. Deploy Web Application Firewalls (WAFs) configured to detect and block SQL injection patterns, including out-of-band techniques.
  4. Monitor network traffic for unusual outbound DNS or HTTP requests that could indicate OOB data exfiltration attempts.
  5. Restrict database user privileges to the minimum necessary to limit the impact of a successful injection.
  6. Implement logging and alerting mechanisms focused on anomalous database queries and application behavior.
  7. Engage in regular security assessments and penetration testing targeting SQL injection vectors.
  8. Coordinate with the vendor for timely patch releases and apply updates as soon as they become available.
  9. Educate development and security teams about OOB SQL injection risks and detection methods.
  10. Consider network segmentation to isolate critical systems and reduce lateral movement opportunities.

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_evaluacion' in '/evaluacion_objetivos_evalua_definido.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.

References

Community reviews

Loading reviews…