/

CVE-2026-75417

Severity:

HIGH RISK

(7.2)

SQL Injection (CWE-89) in YzmCMS Admin Category Controller

CVE-2026-75417

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Unauthorized Database Access and Manipulation

Severity:

HIGH RISK

(7.2)

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 SQL injection vulnerability in YzmCMS 7.5 allows an authenticated administrator to influence a database query through the parentid parameter used by the category management controller. Under deployments where an administrator account can reach the vulnerable function, boolean-based blind injection may enable unauthorized database access or manipulation.

Affected context

The issue occurs in the administrative category-management functionality of YzmCMS 7.5, specifically in the get_arrchildid() function. Risk is present when the function receives the parentid parameter from an authenticated request and incorporates it into a FIND_IN_SET() SQL expression without adequate parameterization or validation.

Exploit preconditions

  • Attack surface: YzmCMS administrative category-management endpoint
  • Required access: A valid authenticated administrator account or equivalent access to the affected function
  • Trigger point: Processing of the user-controlled parentid parameter by get_arrchildid()
  • Why exploitation is possible: The parameter is concatenated into a SQL clause, allowing query logic to be influenced rather than treated strictly as data

Why this happens

The underlying bug is the construction of a database query by concatenating user-controlled input into a FIND_IN_SET() expression. Without parameterized queries, rigorous input handling, and context-appropriate validation, database syntax can be interpreted as part of the command. This behavior maps to CWE-89, SQL Injection, because untrusted input changes the intended structure or behavior of a SQL statement.

Potential impact

  • An attacker may retrieve sensitive database contents through blind query inference.
  • An attacker could modify or delete application data.
  • Database credentials, user records, and configuration data may be exposed.
  • The application could experience unauthorized administrative or business-state changes.
  • Compromise of database-connected services could enable further intrusion.

General mitigation guidance

Mitigation generally focuses on ensuring that all database queries treat

external input as data rather than executable SQL.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for the FIND_IN_SET() operation.
  • Apply strict allowlist validation to identifiers and expected numeric values.
  • Keep database accounts limited to the privileges required by the application.
  • Separate administrative database capabilities from broader operational accounts.
  • Centralize query construction and security review for database-facing code.
  • Avoid exposing database errors or query behavior through administrative responses.
  • Apply defense-in-depth controls such as database activity monitoring and network restrictions.

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag string concatenation or interpolation in SQL queries.
  • Code review checks for database calls receiving request parameters without binding.
  • Tests that verify unexpected input is handled as a value and cannot alter query behavior.
  • Monitoring for unusual administrative query patterns, repeated conditional requests, or abnormal database access.
  • Policy enforcement requiring prepared statements and approved database-access abstractions.
  • Neutral automated code-review or software-composition tools that identify common injection patterns.

Sources

SourceLink
github.comgithub.com/TKar0/TKar0-CvePoc/tree/main/2026-CVE-POC/CVE-2026-75417
github.comgithub.com/yzmcms/yzmcms
github.comgithub.com/TKar0/TKar0-CvePoc/blob/main/2026-CVE-POC/CVE-2026-75417/CVE-2026-75417.md

Frequently asked

questions

It may be exploitable through the YzmCMS administrative interface when the

affected endpoint is network-accessible and the attacker has suitable

authenticated access.

Yes, the described attack path requires an authenticated administrator account

or comparable permission to invoke the vulnerable category-management

functionality.

Replace SQL string concatenation with parameterized queries or prepared

statements, and validate the parameter against the narrowest expected input

format.

Enforce secure database-access patterns in code review and CI, use least

privilege for application database accounts, and monitor administrative

requests and database activity for anomalous behavior.

Find out what's already
exploitable in your codebase.