dbcve.org
Smart S42 Management PlatformApplication · Byzoro

CVE-2024-1918

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-27
Fix available
A fix is available. Upgrade to after 20240219 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A vulnerability has been found in Byzoro Smart S42 Management Platform up to 20240219 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /useratte/userattestation.php. The manipulation of the argument hidwel leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-254839. 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

Unrestricted file upload vulnerability in Byzoro Smart S42 Management Platform's /useratte/userattestation.php. The hidwel parameter accepts arbitrary file uploads without proper validation, allowing remote attackers to upload malicious files. Combined with the ability to execute these files, this can lead to remote code execution.

MitigationImplement strict file type validation (allowlist approach), verify file content/magic bytes, sanitize filenames, and store uploaded files outside the web root. Restrict execution permissions on upload directories.

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
Smart S42 Management PlatformApplication
Affected:<= 20240219

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. Identify Byzoro Smart S42 version
    Locate the installation directory or admin interface for version information. Check system files, license information, or the main login page for a build date or version number matching 20240219 or earlier.
    Affected if The installed version is unknown, unverified, or shows a build date on or before February 19, 2024.
  2. Verify the vulnerable endpoint exists
    Attempt to access /useratte/userattestation.php via HTTP or HTTPS on the web server. A 200 or 403 response indicates the file exists. Use a tool like curl: curl -I https://[target]/useratte/userattestation.php
    Affected if The endpoint returns a valid HTTP response (not 404), indicating the file is present and accessible.
  3. Confirm the upload parameter is accepted
    Send a test POST request to /useratte/userattestation.php with a basic file in the hidwel parameter. Check if the application accepts and processes the upload without rejecting it based on file type.
    Affected if The application accepts a file upload via the hidwel parameter without performing rigorous file type validation.
  4. Check upload directory execution permissions
    Inspect the web server configuration and the directory where uploaded files are stored. Look for lack of restrictions on script execution within the upload directory (check for lack of AddHandler or RemoveHandler directives in Apache, or similar IIS configurations).
    Affected if Uploaded files can be stored in a directory that permits script execution, or the server configuration does not block execution of uploaded file types.
  5. Assess network exposure of the management interface
    Determine if the Byzoro management platform web interface is exposed to untrusted networks. Check firewall rules, access control lists, or reverse proxy configurations that govern access to the /useratte/ path.
    Affected if The /useratte/userattestation.php endpoint is reachable from untrusted or external networks without authentication barriers.

You are affected if Byzoro Smart S42 Management Platform version 20240219 or earlier is running, the /useratte/userattestation.php endpoint is accessible, and the upload functionality accepts files without strict validation and permits execution of uploaded content.

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
Upgrade available Upgrade to a release after 20240219
Interim mitigation

Implement strict file type validation (allowlist approach), verify file content/magic bytes, sanitize filenames, and store uploaded files outside the web root. Restrict execution permissions on upload directories.

Fix this in Smart S42 Management Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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