dbcve.org
Evaluacion De DesempenoApplication · Quatuor

CVE-2026-1474

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' en ‘/evaluacion_inicio.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

OOB SQL injection vulnerability in the Performance Evaluation (EDD) application by Gabinete Técnico de Programación. The Id_usuario and Id_evaluacion parameters in /evaluacion_inicio.aspx are vulnerable, allowing attackers to extract sensitive data through external channels (DNS, HTTP callbacks) since the application does not return query results directly.

MitigationImplement parameterized queries (prepared statements) for Id_usuario and Id_evaluacion parameters in /evaluacion_inicio.aspx. Apply input validation as defense-in-depth and deploy a WAF as an interim control until the fix is applied.

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 Quatuor Evaluacion De Desempeno installation
    Locate the application on the server. Check for the presence of evaluacion_inicio.aspx in the web root directory or application folder. Common paths may include /inetpub/wwwroot/, /var/www/, or the application's designated web directory.
    Affected if The application file evaluacion_inardo exists on the system and is accessible via web server.
  2. Verify vulnerable endpoint is exposed
    Confirm that /evaluacion_inicio.aspx is accessible over HTTP/HTTPS. Check the web server configuration (IIS, Apache, Nginx) for URL routing rules that expose this endpoint.
    Affected if The endpoint /evaluacion_inicio.aspx is reachable and accepts requests.
  3. Identify parameter handling
    Review the source code or decompiled binaries of evaluacion_inicio.aspx. Locate the code handling Id_usuario and Id_evaluacion parameters to determine if they are passed directly to SQL queries without parameterized queries.
    Affected if The Id_usuario or Id_evaluacion parameters are used in SQL queries without prepared statements or stored procedures.
  4. Check application logs for SQL injection patterns
    Review web server logs and application logs for unusual patterns in Id_usuario and Id_evaluacion parameters. Look for SQL syntax characters (quotes, semicolons, UNION, comments) in these parameter values.
    Affected if Logs show SQL syntax characters or patterns indicative of injection attempts against these parameters.
  5. Inspect database query logging
    Enable and review database query logs (SQL Server, MySQL, PostgreSQL) for the application database. Look for queries containing Id_usuario or Id_evaluacion values that include unexpected SQL fragments or unusual timing patterns.
    Affected if Database logs reveal queries with malformed or suspicious input in Id_usuario or Id_evaluacion fields.

A system is affected if Quatuor Evaluacion De Desempeno is installed and the /evaluacion_inicio.aspx endpoint accepts Id_usuario or Id_evaluacion parameters that are processed through dynamic SQL queries without parameterized statements.

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 (prepared statements) for Id_usuario and Id_evaluacion parameters in /evaluacion_inicio.aspx. Apply input validation as defense-in-depth and deploy a WAF as an interim control until the fix is applied.

Fix this in Evaluacion De Desempeno Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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