⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.3

How to Fix CVE-2026-1473: SQL Injection in Evaluación de Desempeño (EDD)

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 9.3 - Critical
Actively exploited?Not currently listed in CISA KEV
AffectedAll versions
Fixed inSee vendor advisory
Type (CWE)CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

What is CVE-2026-1473?

CVE-2026-1473 is a SQL injection flaw in Evaluación de Desempeño (EDD). User input reaches a database query without proper parameterization, letting an attacker read, modify, or in some cases execute commands through stacked queries or out-of-band channels. Vendor description: 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_competencias_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.

Why this CVE matters

SQL injection against a management product is rarely just a data leak. Once an attacker can read or write to the application database, the chain commonly ends with credential theft, persistence via scheduled tasks, or stacked queries that pivot into the operating system.

For deployments of Evaluación de Desempeño (EDD) that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open Evaluación de Desempeño (EDD)'s About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-1473

The fix is to apply the patched build listed in the Quatuor advisory.

Affected versions confirmed in the CVE record:

Patch via the OS package manager (Linux)


<!-- enrich_agent_2:v1 -->
# 1. Update the package metadata.
sudo apt update                                  # Debian / Ubuntu
sudo dnf check-update                            # RHEL / Rocky / AlmaLinux / Fedora
sudo zypper refresh                              # openSUSE

# 2. Pull the patched version listed in the [vendor advisory](https://www.incibe.es/en/incibe-cert/notices/aviso/out-band-sql-injection-quatuor-performance-evaluation) of Evaluación de Desempeño (EDD) from Quatuor.
sudo apt install --only-upgrade evaluaci-n-de-desempe-o-edd
sudo dnf upgrade evaluaci-n-de-desempe-o-edd
sudo zypper update evaluaci-n-de-desempe-o-edd

# 3. Restart the affected service so the patched binary is the running binary.
sudo systemctl restart evaluaci-n-de-desempe-o-edd || true

# 4. Verify the running version.
evaluaci-n-de-desempe-o-edd --version

Verify the fix worked


<!-- enrich_agent_2:v1 -->
# 1. Confirm the running version matches the fixed-in version from the advisory.
#    Cross-check against the vendor advisory: https://www.incibe.es/en/incibe-cert/notices/aviso/out-band-sql-injection-quatuor-performance-evaluation

# 2. Re-scan with your vulnerability scanner. The scanner should no longer flag
#    this CVE on the patched host.
# Example with Nmap NSE:
nmap -sV --script vuln <target-host>

# 3. Inspect the service / kernel logs for crash-loops or rollback events in
#    the first hour after the upgrade.
journalctl -u <service-name> --since "1 hour ago"
dmesg --since "1 hour ago"

If you cannot patch immediately

Front the affected endpoint with a WAF rule that blocks SQL metacharacters in the vulnerable parameters. This is a stopgap, not a fix. Patch promptly.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in Evaluación de Desempeño (EDD), scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-1473 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-1473?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Do I need to assume compromise if my Evaluación de Desempeño (EDD) was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*