dbcve.org
Evaluacion De DesempenoApplication · Quatuor

CVE-2026-1478

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' and 'Id_evaluacion’ in ‘/evaluacion_hca_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 · high confidence

An out-of-band SQL injection vulnerability exists in the Performance Evaluation (EDD) application by Gabinete Técnico de Programación. The vulnerability resides in the 'Id_usuario' and 'Id_evaluacion' parameters at the '/evaluacion_hca_evalua.aspx' endpoint. Unlike standard SQLi, this OOB variant exfiltrates data through external channels (e.g., DNS, HTTP requests) since the application does not return query results directly, allowing attackers to extract sensitive database information.

MitigationFix by replacing dynamic SQL queries with parameterized queries or stored procedures for both 'Id_usuario' and 'Id_evaluacion' parameters, and implement strict input validation to prevent OOB data exfiltration.

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. Confirm the Quatuor Evaluacion De Desempeno application is installed
    Check for the application by searching for its installation directory, service, or web application files on the server. Look for the 'evaluacion_hca_evalua.aspx' file in the web root.
    Affected if The application is present and the affected aspx file exists on the system.
  2. Verify the application is reachable via network
    Attempt to access the affected endpoint 'http[s]://[host]/evaluacion_hca_evalua.aspx' using a web browser or curl command to confirm the application is exposed.
    Affected if The endpoint responds with any HTTP status code, indicating the application is running and accessible.
  3. Identify if user input is accepted on the affected parameters
    Review application forms, URLs, or API calls that pass 'Id_usuario' or 'Id_evaluacion' parameters to the /evaluacion_hca_evalua.aspx endpoint. Check if these parameters accept user-supplied values without apparent sanitization.
    Affected if The application accepts input for Id_usuario or Id_evaluacion parameters without requiring authentication or showing evidence of input validation.
  4. Monitor for outbound network connections from the application
    Use network monitoring tools (e.g., Wireshark, network taps, or web application firewall logs) to observe if the application initiates outbound DNS or HTTP requests to unexpected external domains when the affected parameters are manipulated.
    Affected if The application generates outbound DNS lookups or HTTP requests to attacker-controlled domains when SQL-like input is provided in Id_usuario or Id_evaluacion parameters.
  5. Review application logs for SQL injection indicators
    Examine web server logs, application event logs, or database logs for unusual SQL syntax, error messages, or patterns consistent with SQL injection attempts against the affected endpoint.
    Affected if Logs contain SQL syntax errors, database error messages, or unusual query fragments referencing the Id_usuario or Id_evaluacion parameters.

The environment is affected if the Quatuor Evaluacion De Desempeno application is running and the /evaluacion_hca_evalua.aspx endpoint with Id_usuario or Id_evaluacion parameters is exposed to users or attackers.

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

Fix by replacing dynamic SQL queries with parameterized queries or stored procedures for both 'Id_usuario' and 'Id_evaluacion' parameters, and implement strict input validation to prevent OOB data exfiltration.

Fix this in Evaluacion De Desempeno Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1478 — 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-1478 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