dbcve.org
Evaluacion De DesempenoApplication · Quatuor

CVE-2026-1473

HIGH · 7.5 CVSS v3.1 Published 2026-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Out-of-band SQL injection (OOB SQLi) vulnerability in the Performance Evaluation (EDD) application by Gabinete Técnico de Programación. The 'Id_usuario' parameter in '/evaluacion_competencias_evalua.aspx' allows attackers to inject malicious SQL queries that exfiltrate sensitive database information through external channels (DNS, HTTP requests, etc.), bypassing application responses.

MitigationImplement parameterized queries or prepared statements for all database interactions involving the Id_usuario parameter. Apply input validation, restrict database user privileges, and consider deploying a WAF with SQLi detection rules as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Evaluacion De DesempenoApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Quatuor Evaluacion De Desempeno is installed
    Check for the application by searching for 'evaluacion_competencias_evalua.aspx' in web directories or by listing installed applications on the web server.
    Affected if The application files are present on the server.
  2. Confirm the vulnerable endpoint exists
    Access or enumerate the path '/evaluacion_competencias_evalua.aspx' on the web server and verify it returns a valid response.
    Affected if The endpoint responds (indicating the application is present and accessible).
  3. Check if Id_usuario parameter is processed
    Review application source code or captured traffic for requests to the affected endpoint containing the 'Id_usuario' parameter.
    Affected if The application processes requests with the Id_usuario parameter without parameterization.
  4. Identify if external network outbound is possible from the server
    Check server firewall rules and network segmentation to determine if the database server can initiate outbound DNS or HTTP connections to attacker-controlled domains.
    Affected if The server or database backend can make outbound DNS/HTTP requests to external addresses.
  5. Review database user privileges
    Inspect the database user credentials used by the application to determine if they have excessive privileges (e.g., ability to run xp_dirtree, OLE automation, or UDFs for OOB exfiltration).
    Affected if The application database user has privileges that enable OOB data exfiltration techniques.

A user is affected if Quatuor Evaluacion De Desempeno is installed and the /evaluacion_competencias_evalua.aspx endpoint is accessible while processing the Id_usuario parameter without parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for all database interactions involving the Id_usuario parameter. Apply input validation, restrict database user privileges, and consider deploying a WAF with SQLi detection rules as a defense-in-depth measure.

Fix this in Evaluacion De Desempeno Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1473 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data