Skip to main content
VulnerabilityPublished

CVE-2026-1483: 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, 14:05 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

Immediate mitigation should focus on implementing strict input validation and sanitization for the 'Id_usuario' parameter, ensuring that only expected data types and formats are accepted. Developers should refactor the affected code to use parameterized queries or stored procedures to eliminate direct concatenation of user input into SQL commands. Deploying a web application firewall (WAF) with custom rules to detect and block SQL injection patterns, especially those indicative of OOB techniques, can provide an additional layer of defense. Network monitoring should be enhanced to detect unusual outbound DNS or HTTP requests originating from database servers, which may indicate exploitation attempts. Organizations should conduct thorough code audits of all web-facing applications to identify similar injection points. Until official patches are released, isolating the application environment and restricting database server outbound connectivity can reduce exfiltration risks. Regular security training for developers and administrators on secure coding practices and vulnerability awareness is also recommended. Finally, organizations should prepare incident response plans specific to SQL injection attacks 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_ver_auto.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…