dbcve.org
Evaluacion De DesempenoApplication · Quatuor

CVE-2026-1483

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_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.

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

An out-of-band (OOB) SQL injection vulnerability exists in the Performance Evaluation (EDD) application by Gabinete Técnico de Programación. The vulnerability resides in the 'Id_usuario' parameter of the '/evaluacion_objetivos_ver_auto.aspx' endpoint. Attackers can exploit this to exfiltrate sensitive database information through external channels (e.g., DNS, HTTP requests) rather than through direct application responses, bypassing typical output validation.

MitigationRemediate by implementing parameterized queries or prepared statements for the Id_usuario parameter and all user-supplied inputs. Apply strict input validation, least-privilege database accounts, and consider network-level controls to block outbound exfiltration attempts.

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 application is installed
    Check for the application in the system registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall), or look for the web application files in the IIS/web server document root (typically C:\inetpub\wwwroot\ or /var/www/)
    Affected if The application is present on the system
  2. Verify the vulnerable endpoint exists
    Check if the file 'evaluacion_objetivos_ver_auto.aspx' exists in the web application's directory structure. If the application is hosted, attempt to access the endpoint via HTTP GET request to /evaluacion_objetivos_ver_auto.aspx
    Affected if The endpoint returns a valid HTTP response (200 or similar) rather than 404
  3. Confirm the Id_usuario parameter is accepted
    Submit a request to the endpoint with a test value for Id_usuario parameter (e.g., /evaluacion_objetivos_ver_auto.aspx?Id_usuario=1) and observe if the application processes it without error or sanitization
    Affected if The parameter is accepted and the application does not reject or sanitize the input
  4. Check for basic input validation on Id_usuario
    Review application logs or attempt to inject SQL metacharacters (e.g., Id_usuario=1' OR '1'='1) to see if the application blocks or escapes special characters
    Affected if The application accepts SQL special characters without proper escaping or parameterized handling

If the Quatuor Evaluacion De Desempeno application is installed and the /evaluacion_objetivos_ver_auto.aspx endpoint with the Id_usuario parameter is accessible and accepts unsanitized input, the environment is affected by this SQL injection vulnerability.

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 the Id_usuario parameter and all user-supplied inputs. Apply strict input validation, least-privilege database accounts, and consider network-level controls to block outbound exfiltration attempts.

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-1483 — 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-1483 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