CVE-2023-7191
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 · uneditedA vulnerability, which was classified as critical, was found in S-CMS up to 2.0_build20220529-20231006. This affects an unknown part of the file member/reg.php. The manipulation of the argument M_login/M_email leads to sql injection. The exploit has been disclosed to the public and may be used. The identifier VDB-249393 was assigned to this vulnerability. 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 confidenceSQL injection vulnerability in S-CMS member/reg.php via the M_login and M_email parameters. Attackers can manipulate SQL queries through unsanitized user input during registration, potentially allowing unauthorized data access or account takeover.
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= 1.0= 1.5= 2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if S-CMS is installedLocate the S-CMS installation by checking web server document roots for S-CMS directories, or search for characteristic S-CMS files such as index.php, config.php, or the member/ folder structure.Affected if S-CMS is present on the server in any directory.
-
Determine the installed S-CMS versionCheck the version file, changelog, or footer of the CMS for the exact version number. Common locations include a /version file, footer.php, or the administration panel about page.Affected if The installed version matches 1.0, 1.5, or 2.0.
-
Verify the vulnerable reg.php file existsLocate the member/reg.php file within the S-CMS installation directory and confirm it is present on the filesystem.Affected if The file member/reg.php exists in the S-CMS installation.
-
Confirm registration functionality is enabledCheck the S-CMS configuration files or admin settings to determine whether user registration is enabled. This may be in config files under a setting like 'allow_register' or similar, or accessible via the admin control panel.Affected if User registration is enabled or publicly accessible without administrative restriction.
-
Inspect the vulnerable code pathExamine the member/reg.php source code for unsanitized use of M_login and M_email parameters in SQL queries. Look for direct insertion of these POST parameters into SQL statements without escaping or parameterized queries.Affected if The code contains direct SQL query construction using M_login or M_email without input sanitization or prepared statements.
A user is affected if S-CMS versions 1.0, 1.5, or 2.0 are installed with the member/reg.php file present and user registration enabled, exposing the unsanitized M_login and M_email parameters in SQL queries.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized prepared statements for M_login and M_email inputs, or apply vendor security patch if available. If vendor remains unresponsive, implement input validation and whitelist-based sanitization as compensating controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-7191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-7191 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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