CVE-2024-55516
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 Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 v3.90. The component affected by this issue is /upload_sysconfig.php on the web interface. By crafting a suitable form name, arbitrary files can be uploaded, potentially leading to unauthorized access to server permissions.
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 confidenceArbitrary file upload vulnerability in Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 devices running v3.90. The /upload_sysconfig.php component on the web interface allows attackers to craft a form name to upload arbitrary files to the server, potentially achieving unauthorized access and privilege escalation.
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= 3.90= 3.90= 3.90= 3.90CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 device modelAccess the device web interface or check SNMP/sysinfo to confirm the model is one of MSG1200, MSG2100E, MSG2200, or MSG2300Affected if Device model is NOT one of these four models
-
Check firmware versionNavigate to the device web management interface and locate the firmware/version information (typically under System, Status, or About sections), or query the device via SNMP or CLI using 'show version' or equivalent commandAffected if Firmware version is EXACTLY 3.90 (only this exact version is affected)
-
Verify web management interface accessibilityAttempt to access the device web interface over HTTP/HTTPS from an external or untrusted network segmentAffected if The web management interface is accessible from untrusted networks
-
Confirm upload_sysconfig.php endpoint existsAttempt to access /upload_sysconfig.php on the device (e.g., http://<device-ip>/upload_sysconfig.php)Affected if The endpoint returns a response (indicating it exists and may be accessible)
-
Check authentication configurationReview the web interface authentication settings to determine if authentication is required for the upload functionality, or attempt to access the endpoint without valid credentialsAffected if The upload endpoint is accessible without proper authentication or uses weak authentication
The environment is affected if the device is a Raisecom MSG1200, MSG2100E, MSG2200, or MSG2300 running firmware version 3.90 with the /upload_sysconfig.php endpoint accessible (with or without valid 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 dataImmediately restrict network access to the web interface, implement WAF rules to block malicious upload requests, and apply vendor firmware patches when available. Consider disabling the affected upload functionality if not required for operations.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55516 — 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-55516 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