CVE-2026-1475
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 · uneditedAn 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_acciones_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 confidenceOut-of-band SQL injection vulnerability in the Id_usuario parameter of /evaluacion_acciones_evalua.aspx in the Performance Evaluation (EDD) application. The flaw allows attackers to extract sensitive database information through external channels (e.g., DNS or HTTP callbacks) without the application returning data directly in the response.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Quatuor Evaluacion De Desempeno installationLocate the web application files on the server or identify the running web service hosting the Performance Evaluation (EDD) application. Check for the presence of evaluacion_acciones_evalua.aspx or related .aspx files in the web root directory.Affected if The Quatuor Evaluacion De Desempeno application is present on the system.
-
Identify the vulnerable endpointLocate or access the URL path /evaluacion_acciones_evalua.aspx within the application. Verify that this page accepts the Id_usuario parameter in GET or POST requests.Affected if The page /evaluacion_acciones_evalua.aspx exists and accepts the Id_usuario parameter.
-
Check parameter handling for SQL injection vectorsExamine how the Id_usuario parameter processes input. Look for direct string concatenation in SQL queries or lack of parameterized query usage in the application code or logs. Test by submitting a benign value like Id_usuario=1 to observe the application's behavior.Affected if The Id_usuario parameter appears to concatenate user input directly into SQL queries without using parameterized queries or prepared statements.
-
Detect out-of-band SQL injection activityMonitor for unexpected outbound DNS queries, HTTP requests, or network connections originating from the application server to external domains after submitting SQL payloads in the Id_usuario parameter. Review DNS logs, WAF/IDS logs, or network traffic for patterns indicative of out-of-band injection (e.g., DNS lookups to attacker-controlled domains).Affected if The application makes unexpected outbound network callbacks (DNS/HTTP) to external systems when SQL injection payloads are submitted via Id_usuario, indicating successful out-of-band SQL injection.
A user is affected if the Quatuor Evaluacion De Desempeno application is installed, the /evaluacion_acciones_evalua.aspx page with the Id_usuario parameter exists, and the parameter does not use parameterized queries, as evidenced by successful out-of-band SQL injection testing or network traffic analysis.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries or prepared statements for the Id_usuario parameter and add proper input validation. Consider deploying a WAF as an additional layer of defense while code fixes are implemented.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-1475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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