dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4234

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A security flaw has been discovered in SSCMS 7.4.0. This vulnerability affects unknown code of the file SitesAddController.Submit.cs of the component DDL Handler. The manipulation of the argument tableHandWrite results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

SQL injection vulnerability in SSCMS 7.4.0's DDL Handler component (SitesAddController.Submit.cs). The 'tableHandWrite' argument is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code.

MitigationReplace dynamic SQL construction with parameterized queries/prepared statements for the tableHandWrite argument in SitesAddController.Submit.cs. Apply input validation and ensure database accounts follow least privilege principles.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 version
    Locate the version file or assembly information for the SSCMS installation. Common locations include: version.json, About page in admin panel, or the main DLL file properties. Compare the installed version to 7.4.0.
    Affected if The installed SSCMS version is 7.4.0 exactly, or falls within the 7.x range prior to any security patch.
  2. Locate SitesAddController.Submit.cs
    Search the SSCMS installation directory for the file SitesAddController.Submit.cs, typically found in the /Controllers/ or /Areas/ directory structure of the web application.
    Affected if The file exists in the installation, indicating the vulnerable component is present.
  3. Verify DDL Handler feature is enabled
    Check the SSCMS configuration files (typically in /config/ or appsettings.json) for DDL Handler module/enabled settings, or verify access to the SitesAddController endpoint through the application's routing.
    Affected if The DDL Handler functionality is enabled or accessible in the application.
  4. Inspect tableHandWrite parameter handling
    Open SitesAddController.Submit.cs and locate the code handling the 'tableHandWrite' parameter. Search for direct string concatenation or unsanitized string interpolation in SQL query construction.
    Affected if The code shows direct use of tableHandWrite in SQL queries without parameterized queries, prepared statements, or input sanitization.
  5. Review database query logs
    Enable and review database query logging or SQL Profiler traces. Look for SQL queries containing the tableHandWrite parameter that show anomalous SQL syntax indicative of injection attempts.
    Affected if Suspicious SQL patterns appear in database logs, or queries contain unexpected SQL operators/commands passed through the tableHandWrite argument.

A user is affected if SSCMS version 7.4.0 is installed, the SitesAddController.Submit.cs file exists, and the tableHandWrite parameter is used in SQL queries without proper sanitization or parameterized queries.

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

Replace dynamic SQL construction with parameterized queries/prepared statements for the tableHandWrite argument in SitesAddController.Submit.cs. Apply input validation and ensure database accounts follow least privilege principles.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4234 — 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-4234 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