/

CVE-2026-90708

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Yot CMS Cookie Handler Login

CVE-2026-90708

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise, authentication impact, and potential unauthorized access

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity SQL injection vulnerability in Yot CMS affects the Login function in the Cookie Handler component. A remote attacker may manipulate login-related inputs to alter database queries, potentially exposing data or affecting authentication and application behavior.

Affected context

The vulnerability occurs in Yot CMS versions up to 3.3.1 when the Login function in global.php processes the yot3_user and yot3_pass parameters without adequately separating user-controlled data from SQL statements. It is relevant to deployments where this login functionality is reachable through a remote application interface.

Exploit preconditions

  • Attack surface: The remotely accessible Yot CMS login endpoint
  • Required access: Network access to the affected application; a valid account may not be required
  • Trigger point: Processing of the yot3_user or yot3_pass parameters by the Cookie Handler Login function
  • Why exploitation is possible: User-controlled input can influence database query construction when parameter handling and query execution are not safely separated

Why this happens

The underlying bug is an injection flaw in which externally supplied login values are incorporated into SQL processing without reliable parameterization or equivalent query-boundary protection. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection). CWE-74 is also relevant as a broader classification for improper neutralization of special elements in interpreted commands.

Potential impact

  • An attacker may retrieve or modify database records
  • Authentication checks could be weakened or bypassed
  • Sensitive application or user data could be exposed
  • Database availability or integrity could be affected
  • The application could be used as a stepping stone for broader compromise, depending on database privileges

General mitigation guidance

Mitigation generally focuses on ensuring that all database operations use parameterized queries or safe query-builder abstractions rather than string-concatenated SQL.

Common defensive patterns include:

  • Treating all request parameters as untrusted input
  • Applying strict input validation appropriate to each field
  • Using least-privilege database accounts with only required permissions
  • Avoiding detailed database errors in externally visible responses
  • Separating authentication logic from unsafe dynamic query construction
  • Adding automated regression tests for injection-resistant database access

How teams detect issues like this

Organizations can look for:

  • Static analysis findings involving string concatenation or interpolation in SQL statements
  • Code review signals where request parameters flow directly into database queries
  • Web application firewall or API gateway rules for suspicious SQL-oriented request patterns
  • Database logs showing abnormal query syntax, repeated authentication probing, or unusual data access
  • Security tests that verify login parameters are passed through parameterized query interfaces

Automated code review and software composition analysis tools may help identify unsafe query construction patterns early.

Sources

SourceLink
github.comgithub.com/dddwmr/CVE/blob/main/YOT%20III%20cookie%20auto-login%20SQL%20injection%20enables%20forged%20administrator%20sessions%20.md
vuldb.comvuldb.com/cve/CVE-2026-90708
vuldb.comvuldb.com/submit/918272
vuldb.comvuldb.com/vuln/403250
vuldb.comvuldb.com/vuln/403250/cti

Frequently asked

questions

Yes. The affected login functionality is remotely reachable, so an attacker with network access to the application may be able to target it without local system access.

The login endpoint is the attack surface, and authentication may not be required. Actual access requirements depend on the deployment's routing, access controls, and request filtering.

Use parameterized database queries or trusted query-builder abstractions, combined with context-appropriate input validation and least-privilege database permissions.

Establish secure database access standards, review all user-input-to-query data flows, test authentication paths for injection resistance, and monitor database activity for anomalous requests.

Find out what's already
exploitable in your codebase.