dbcve.org
Evaluacion De DesempenoApplication · Quatuor

CVE-2026-1480

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_objetivos_anyo_sig_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

A high-severity out-of-band SQL injection vulnerability exists in the Performance Evaluation (EDD) application. The vulnerability resides in the 'Id_usuario' parameter of the '/evaluacion_objetivos_anyo_sig_evalua.aspx' endpoint. Attackers can exploit this to exfiltrate database contents through external channels (e.g., DNS, HTTP requests) since the application does not return the extracted data directly in its response.

MitigationRemediate by implementing parameterized queries or prepared statements for all SQL interactions involving the 'Id_usuario' parameter. Additionally, apply input validation and restrict database permissions to limit exfiltration potential.

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. Identify if Quatuor Evaluacion De Desempeno application is installed
    Review installed applications or web server directories for presence of the EDD/Performance Evaluation application. Check web server logs for access to '/evaluacion_objetivos_anyo_sig_evalua.aspx' endpoint.
    Affected if The application is present and the vulnerable endpoint is accessible on the server.
  2. Confirm the affected endpoint exists
    Check web server configuration or scan for the presence of '/evaluacion_objetivos_anyo_sig_evalua.aspx' in the application's web directory.
    Affected if The endpoint file exists in the application's web root.
  3. Verify the application processes the Id_usuario parameter
    Review application source code or web application firewall (WAF) logs for requests hitting the endpoint with the Id_usuario parameter. If you have access to the code, search for SQL queries that directly incorporate the Id_usuario parameter without parameterized queries.
    Affected if The application processes Id_usuario in SQL queries without proper sanitization or parameterized queries.
  4. Check database access logs for suspicious outbound exfiltration patterns
    Review DNS query logs, HTTP outbound logs, and database audit logs for unusual patterns indicating data exfiltration through DNS or HTTP channels originating from the application server.
    Affected if Unusual DNS or HTTP requests containing database-like data patterns are observed from the application server.

If the Quatuor Evaluacion De Desempeno application is installed and the vulnerable endpoint is accessible, the environment is affected since all versions contain the SQL injection flaw in the Id_usuario parameter.

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

Remediate by implementing parameterized queries or prepared statements for all SQL interactions involving the 'Id_usuario' parameter. Additionally, apply input validation and restrict database permissions to limit exfiltration potential.

Fix this in Evaluacion De Desempeno Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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