CVE-2026-7435: SSCMS v7.4.0 SQL Injection via stl:sqlContent queryString
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.
Security readout for executives and security teams
Plain-English summary
SSCMS 7.4.0 contains a high-severity flaw that may let a sufficiently privileged remote attacker make the application execute unintended database commands. Successful exploitation could expose or alter data, bypass authentication, disrupt service, or compromise the database. The supplied sources do not establish active exploitation or identify a fixed release.
Executive priority
Treat confirmed SSCMS 7.4.0 exposure as an urgent remediation item because successful exploitation could affect database confidentiality, integrity, and availability. Immediately inventory deployments and reduce endpoint exposure while obtaining vendor guidance. Escalate faster where the application handles sensitive data or uses an overprivileged database account.
Technical view
The stl:sqlContent tag passes its queryString attribute to database execution without parameterization or sanitization. Crafted encrypted input submitted through /api/stl/actions/dynamic can therefore reach the SQL interpreter. This is CWE-89 with CVSS 4.0 score 8.6. The supplied vector indicates network access, low complexity, no user interaction, and high privileges required.
Likely exposure
Prioritize systems running SSCMS 7.4.0 where /api/stl/actions/dynamic is reachable and relevant stl:sqlContent processing is enabled. The supplied record does not establish whether default configurations are vulnerable, precisely define the required privileges, or identify additional affected versions.
Exploitation context
CISA KEV status is false in the supplied bundle, and no cited source establishes active exploitation. Public technical disclosure may increase attacker awareness. Exploitation reportedly requires crafted encrypted input and, according to the CVSS vector, high privileges; encryption does not address the underlying failure to parameterize SQL.
Researcher notes
Evidence supports an SQL injection data flow from queryString to database execution, but the bundle does not provide a patch identifier, affected configuration matrix, or evidence of exploitation in the wild. The CVSS PR:H rating materially limits exposure compared with an unauthenticated flaw, although the exact privilege prerequisite remains unclear.
Mitigation direction
Inventory SSCMS deployments and prioritize confirmed version 7.4.0 systems.
Check the vendor issue and advisory for an approved fix or updated release.
Restrict access to /api/stl/actions/dynamic until vendor remediation is applied.
Apply least privilege to the application's database account as a compensating control.
Monitor application and database logs for anomalous endpoint activity or unexpected queries.
Validation and detection
Confirm the installed SSCMS version using trusted deployment or package records.
Determine whether /api/stl/actions/dynamic is reachable and document its authentication requirements.
Review templates and content for use of stl:sqlContent with queryString.
Review application and database logs for suspicious requests, errors, or unauthorized changes.
After remediation, verify vendor-prescribed protections and run non-destructive regression testing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.