Sitemagic CmsApplication · Sitemagic

CVE-2023-53921

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
SitemagicCMS 4.4.3 contains a remote code execution vulnerability that allows attackers to upload malicious PHP files to the files/images directory. Attackers can upload a .phar file with system command execution payload to compromise the web application and execute arbitrary system commands.

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

SitemagicCMS 4.4.3 suffers from an insecure file upload vulnerability allowing unauthenticated attackers to upload malicious .phar files containing PHP code with system() calls to the files/images directory. Since .phar files are executable by PHP, attackers can directly execute arbitrary system commands on the server, achieving full remote code execution.

MitigationImplement strict file upload validation (whitelist allowed extensions/MIME types, reject .phar and other executable extensions), store uploads outside webroot or disable PHP execution in upload directories, and remove any existing malicious files from the affected directory.

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
Sitemagic CmsApplication
Affected:= 4.4.3

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Sitemagic CMS version
    Locate the version file or footer in the CMS installation. Common locations include a version.php file, README file, or the admin dashboard. Check the main index.php or configuration files for version strings.
    Affected if The installed version is exactly 4.4.3
  2. Verify files/images directory exists
    Check the web root for the 'files/images' directory. This is the directory where uploads are accepted according to the CVE.
    Affected if The directory exists and is publicly accessible via the web server
  3. List .phar files in upload directory
    Use a file manager or command line to list all files with .phar extension in the files/images directory. Run: ls -la /path/to/webroot/files/images/*.phar or dir /path\to\webroot\files\images\*.phar
    Affected if Any .phar files exist in the files/images directory
  4. Inspect suspicious PHP-related files
    Examine any recently created or modified PHP, phar, or phtml files in the upload directory. Check file contents for system(), exec(), passthru(), or shell_exec() calls.
    Affected if Files containing PHP code with system execution functions exist in the upload directory
  5. Review web server access logs
    Examine web server access logs (Apache access.log, Nginx access.log) for POST requests to upload endpoints targeting the files/images directory. Look for .phar file uploads.
    Affected if Logs show unauthenticated POST requests uploading .phar files to the files/images directory

A system is affected if it runs Sitemagic CMS version 4.4.3 and has publicly accessible .phar files or evidence of unauthorized uploads in the files/images directory.

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 strict file upload validation (whitelist allowed extensions/MIME types, reject .phar and other executable extensions), store uploads outside webroot or disable PHP execution in upload directories, and remove any existing malicious files from the affected directory.

Fix this in Sitemagic Cms 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-2023-53921 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-53921 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