dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-7435

HIGH · 7.2 CVSS v3.1 Published 2026-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

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

MitigationParameterize all SQL queries in the stl:sqlContent tag's queryString attribute and implement proper input validation. If possible, restrict or disable the /api/stl/actions/dynamic endpoint until a patched version is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SSCMS installation and version
    Check the site's about page, administration panel, or examine DLLAssembly versions in the bin directory. Look for files like SiteServer.Core.dll or check the version.json/config file in the installation root.
    Affected if The installed version is SSCMS v7.4.0 exactly, or falls within the v7.4.0 range.
  2. Locate stl:sqlContent tag usage
    Search site templates, pages, and content files for instances of '<stl:sqlContent' or 'stl:sqlContent'. Examine any queryString attribute values to see if they contain dynamic user input or are built from concatenation.
    Affected if The stl:sqlContent tag is in use with a queryString attribute that accepts unsanitized input.
  3. Verify /api/stl/actions/dynamic endpoint exists
    Attempt a GET or POST request to /api/stl/actions/dynamic on the target site. Check if the endpoint responds (even with an error) indicating it is accessible.
    Affected if The endpoint returns any HTTP response (other than 404), confirming the endpoint is enabled.
  4. Review access logs for endpoint activity
    Examine web server (IIS, Nginx) access logs and SSCMS application logs for POST requests to /api/stl/actions/dynamic, particularly those with unusual or encrypted request bodies.
    Affected if There are requests to /api/stl/actions/dynamic originating from unexpected IP addresses or at unusual times.
  5. Audit database for unauthorized changes
    Query the database for recent changes to admin accounts, new users, or modified permissions. Look for unexpected stored procedures, views, or tables created around the time of potential exploitation.
    Affected if Unexpected admin accounts exist, permissions were modified, or unfamiliar database objects were created.

You are affected if SSCMS v7.4.0 is running, the stl:sqlContent tag with queryString is in use, and the /api/stl/actions/dynamic endpoint is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Parameterize all SQL queries in the stl:sqlContent tag's queryString attribute and implement proper input validation. If possible, restrict or disable the /api/stl/actions/dynamic endpoint until a patched version is available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7435 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data