CVE-2024-28520
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 · uneditedFile Upload vulnerability in Byzoro Networks Smart multi-service security gateway intelligent management platform version S210, allows an attacker to obtain sensitive information via the uploadfile.php component.
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 confidenceByzoro Networks Smart multi-service security gateway S210 contains a file upload vulnerability in the uploadfile.php component. Attackers can exploit this to upload files that allow retrieval of sensitive information from the system, likely through path traversal or improper access controls on uploaded files.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the Byzoro S210 gateway productCheck your network device inventory or access the device admin interface to confirm the model is Byzoro Networks Smart multi-service security gateway S210Affected if The device is a Byzoro S210 gateway unit
-
Locate the uploadfile.php componentAccess the web interface or check the webroot directory for the presence of uploadfile.php. Common paths may include /admin/uploadfile.php or /cgi-bin/uploadfile.phpAffected if The uploadfile.php file exists on the device
-
Verify uploadfile.php is web-accessibleAttempt to access uploadfile.php via HTTP/HTTPS from an external endpoint (e.g., curl http://[device-ip]/uploadfile.php) and observe if the script respondsAffected if The script returns a response rather than a 404 or access denied error
-
Check if unauthenticated file upload is possibleSend a test POST request to uploadfile.php with a benign file (e.g., a text file with a .txt extension) without authentication credentials and observe if the upload succeedsAffected if The upload request succeeds and returns a file path or confirmation without requiring login
-
Determine if uploaded files are web-retrievableAfter an upload test, attempt to access the uploaded file via web browser using the returned path (e.g., http://[device-ip]/uploads/test.txt)Affected if The uploaded file can be retrieved via HTTP, indicating improper access controls
You are affected if you are running a Byzoro S210 gateway with an accessible uploadfile.php endpoint that permits unauthenticated file uploads and allows retrieval of those files via the web.
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 dataRestrict or disable the uploadfile.php endpoint, implement strict file type validation and content inspection, ensure uploaded files are stored outside web-accessible directories, and add proper authentication/authorization checks.
- 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-28520 — 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-28520 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