dbcve.org
SiberiancmsApplication

CVE-2023-39378

HIGH · 8.8 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 4.20.44 / 5.0.4 or later.
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
SiberianCMS - CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') by an unauthenticated user

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

SiberianCMS contains a SQL injection vulnerability (CWE-89) that allows unauthenticated attackers to inject malicious SQL commands through improper neutralization of special elements in SQL queries.

MitigationImplement parameterized queries or prepared statements across all database query locations to properly sanitize user inputs before executing SQL commands.

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
SiberiancmsApplication
Affected:>= 4.0.0, < 4.20.44>= 5.0.0, < 5.0.4

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 installed SiberianCMS version
    Locate the version file - typically in a VERSION file in the root directory, or check the admin panel under System > Information. Also check changelog or composer.json if present.
    Affected if The installed version falls within 4.0.0 to <4.20.44 OR 5.0.0 to <5.0.4
  2. Verify web accessibility of the application
    Confirm the CMS is accessible over HTTP/HTTPS. The SQL injection is exploitable by unauthenticated attackers, meaning the vulnerable code paths are reached via the web interface.
    Affected if The application is exposed to network access (either LAN or internet) and processes requests without authentication requirements for the vulnerable endpoints.
  3. Inspect database query code for parameterization
    Review PHP files in the application source code, particularly in libraries/ folder or modules that handle user-supplied data in SQL queries. Look for direct string concatenation or interpolation in SQL statements.
    Affected if Code uses string concatenation, interpolation, or unsanitized variables directly in SQL queries (e.g., "SELECT * FROM users WHERE id = " . $id) rather than prepared statements or parameterized queries.

You are affected if your installed version is 4.0.0 through 4.20.43, or 5.0.0 through 5.0.3, and the application processes SQL queries without proper parameterization.

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.

dbcve · scoped
Upgrade available Upgrade to 4.20.44 / 5.0.4 or later
Fixed in 4.20.445.0.4
Interim mitigation

Implement parameterized queries or prepared statements across all database query locations to properly sanitize user inputs before executing SQL commands.

Recommended fix High confidence

SiberianCMS version 4.20.44 or higher for v4.x, or version 5.0.4 or higher for v5.x

  1. Backup the entire database and all application files before proceeding
  2. Enable maintenance mode or take the site offline to prevent user access during upgrade
  3. Download the fixed version (4.20.44 for v4.x branch or 5.0.4 for v5.x branch) from the official SiberianCMS source
  4. Extract the new version files and upload them to the server, overwriting existing application files
  5. Run any database migration scripts if included in the release
  6. Verify the upgrade was successful by checking the admin panel and testing application functionality
  7. Remove any temporary files or maintenance mode settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Siberiancms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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