CVE-2025-26163: CM Soluces Informatica Ltda Auto Atendimento 1.x.x was discovered to contain a SQL injection via the CPF param
CVE-2025-26163 is a critical-severity flaw (CVSS 9.8) affecting auto atendimento. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
CM Soluces Informatica Ltda Auto Atendimento 1.x.x was discovered to contain a SQL injection via the CPF parameter.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.5% (top 58%) |
| CISA exploited list | No |
| Weakness | CWE-89 |
| Published | 2025-03-14 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-26163?
auto atendimento: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2025-26163 being exploited?
CVE-2025-26163 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-26163 affect?
CVE-2025-26163 affects auto atendimento. Severity is critical (CVSS 9.8). CM Soluces Informatica Ltda Auto Atendimento 1.x.x was discovered to contain a SQL injection via the CPF parameter.
How urgent is CVE-2025-26163?
Priority 55/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2025-30022 MEDIUM 6.8 DOWNGRADE CM Soluces Informatica Ltda Auto Atendimento 1.x.x was discovered to contain a SQL injection via the DATANASC