dbcve.org
S CmsApplication

CVE-2023-7189

HIGH · 8.8 CVSS v3.1 Published 2023-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 vulnerability classified as critical was found in S-CMS up to 2.0_build20220529-20231006. Affected by this vulnerability is an unknown functionality of the file /s/index.php?action=statistics. The manipulation of the argument lid leads to sql injection. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-249391. NOTE: 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 · high confidence

SQL injection vulnerability in S-CMS /s/index.php via the 'lid' parameter in the statistics action allows remote attackers to manipulate database queries. The flaw stems from unsanitized user input being directly incorporated into SQL statements. This high-severity (CVSS 8.8) issue affects all versions up to 2.0_build20231006 and a public exploit exists.

MitigationImplement prepared statements/parameterized queries for the 'lid' parameter and all user-controlled inputs in the statistics functionality. Apply input validation and output encoding as defense-in-depth.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
S CmsApplication
Affected:= 1.0= 1.5= 2.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 S-CMS installation
    Locate the web root directory and look for files named 'index.php' in subdirectories, specifically /s/index.php which contains the vulnerable statistics functionality.
    Affected if S-CMS software is present on the server with the /s/index.php file accessible.
  2. Determine S-CMS version
    Inspect the source code of /s/index.php or any version file in the S-CMS installation for a build version string such as 'build20231006' or compare file timestamps. Check the main index.php or a README file for version identifiers.
    Affected if The installed version is 2.0_build20231006 or earlier, or versions 1.0 or 1.5 of any build.
  3. Verify statistics action is accessible
    Attempt to access /s/index.php?c=statistics (or similar endpoint that triggers the statistics action) via HTTP request. Inspect the application's routing to confirm the 'statistics' action exists and maps to /s/index.php.
    Affected if The statistics functionality is enabled and reachable via the web application.
  4. Test for SQL injection in lid parameter
    Send a crafted HTTP GET request to /s/index.php with the statistics action and a test payload in the 'lid' parameter such as 'lid=1' AND '1'='1 to observe different database behavior or error messages. Compare responses with and without the payload.
    Affected if The application returns different results based on SQL injection payloads in the 'lid' parameter, indicating unsanitized input is used in SQL queries.
  5. Check application logs for exploitation attempts
    Review web server access logs and application error logs for suspicious requests to /s/index.php containing SQL injection patterns in the 'lid' parameter.
    Affected if Log entries show exploitation attempts against the 'lid' parameter, confirming active targeting.

A user is affected if S-CMS versions 1.0, 1.5, or 2.0 up to build 20231006 are installed with the statistics functionality accessible, and the 'lid' parameter accepts unsanitized SQL input.

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

Implement prepared statements/parameterized queries for the 'lid' parameter and all user-controlled inputs in the statistics functionality. Apply input validation and output encoding as defense-in-depth.

Fix this in S Cms 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-2023-7189 — 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-2023-7189 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