CVE-2024-4904
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 was found in Byzoro Smart S200 Management Platform up to 20240507. It has been rated as critical. This issue affects some unknown processing of the file /useratte/userattestation.php. The manipulation of the argument web_img leads to unrestricted upload. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-264437 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 · moderate confidenceAn unrestricted file upload vulnerability exists in Byzoro Smart S200 Management Platform (versions up to 20240507). The vulnerability is in the /useratte/userattestation.php script where the web_img parameter is not properly validated, allowing authenticated remote attackers to upload arbitrary files to the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm Byzoro Smart S200 is installedIdentify if the Byzoro Smart S200 Management Platform web application is running in your environment by checking the application or reviewing your software inventory.Affected if The product is present in your environment.
-
Check the installed versionLocate the version information for your Byzoro Smart S200 Management Platform installation (typically found in the web interface, an about page, or configuration files) and compare it against the affected range: versions up to and including 20240507.Affected if The installed version is 20240507 or earlier.
-
Verify the vulnerable script existsCheck if the file /useratte/userattestation.php exists on your web server by attempting to access it via HTTP/HTTPS or by inspecting the web root directory structure.Affected if The script exists and is accessible via the web.
-
Confirm the upload parameter is presentExamine the userattestation.php script or test the endpoint with the web_img parameter to verify the file upload functionality is present and operational.Affected if The web_img parameter accepts file uploads without proper validation.
-
Assess authentication requirementsDetermine whether the upload endpoint requires valid authentication credentials to access, as the vulnerability affects authenticated users.Affected if The endpoint can be accessed with valid credentials and allows arbitrary file uploads.
You are affected if your Byzoro Smart S200 Management Platform version is 20240507 or earlier and the /useratte/userattestation.php endpoint with the web_img parameter is accessible with authentication.
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 dataImplement strict file type validation, enforce authentication/authorization checks on the upload endpoint, and store uploaded files outside the web root with randomized filenames.
- 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-2024-4904 — 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-2024-4904 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