Skip to main content
CVE-2026-1473VulnerabilityPublished

CVE-2026-1473: 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 25 Oct 2026, 19:02 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 2026-10-25.

What to do

Affected software

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

AI-suggested

To mitigate CVE-2026-1473, organizations should immediately implement strict input validation and sanitization on the 'Id_usuario' parameter to prevent injection of malicious SQL commands. Employing parameterized queries or prepared statements is essential to separate code from data and eliminate injection vectors. Since no official patches are currently available, organizations should consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns, especially those targeting the vulnerable endpoint. Monitoring outbound network traffic for unusual DNS or HTTP requests originating from the database server can help detect OOB SQLi attempts. Restricting database user permissions to the minimum necessary can limit the impact of successful exploitation. Conducting thorough code reviews and security testing of the EDD application is recommended to identify and remediate similar vulnerabilities. Organizations should also prepare incident response plans specific to data exfiltration scenarios and ensure compliance teams are aware of the potential GDPR implications. Finally, maintain close communication with the vendor for forthcoming patches and updates.

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_competencias_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.

References

Community reviews

Loading reviews…