CVE-2026-7435: SSCMS v7.4.0 SQL Injection via stl:sqlContent queryString

Published Apr 30, 2026

Updated

SSCMS v7.4.0 contains a SQL injection vulnerability in the stl:sqlContent tag where the queryString attribute is passed directly to database execution without parameterization or sanitization. Attackers can craft encrypted payloads submitted to the /api/stl/actions/dynamic endpoint to execute arbitrary SQL statements, leading to unauthorized database access, data disclosure, authentication bypass, data modification, or complete database compromise.

Affected Software

1 affected component

sscms SSCMS=7.4.0

Event History

Apr 30, 2026

CVE Published

via MITRE·08:09 PM

Data Sourced

via MITRE·08:09 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·09:16 PM

DescriptionSeverityWeakness

Dec 24, 58314

Event

via FIRST·09:57 AM

Frequently Asked Questions

What is the severity of CVE-2026-7435?

The severity of CVE-2026-7435 is high due to the potential for SQL injection, which can lead to unauthorized access to database information.

How do I fix CVE-2026-7435?

To fix CVE-2026-7435, ensure that all input to the stl:sqlContent queryString attribute is properly parameterized and sanitized before execution.

What software is affected by CVE-2026-7435?

CVE-2026-7435 affects SSCMS version 7.4.0.

Can CVE-2026-7435 lead to data leakage?

Yes, CVE-2026-7435 can lead to data leakage as attackers may execute arbitrary SQL queries to extract sensitive data from the database.

What are the potential attack vectors for CVE-2026-7435?

Attackers can exploit CVE-2026-7435 by crafting malicious payloads that manipulate the stl:sqlContent queryString to execute unauthorized SQL commands.