CVE-2024-50427
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in devsoftbaltic SurveyJS surveyjs.This issue affects SurveyJS: from n/a through <= 1.9.136.
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 confidenceUnrestricted file upload vulnerability in SurveyJS library allows attackers to upload dangerous file types (e.g., executable scripts, webshells) without proper validation. The lack of file type restrictions enables remote code execution if malicious files are uploaded and accessed.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SurveyJS installationSearch for surveyjs-related directories or check your web application inventory for SurveyJS componentsAffected if SurveyJS is present in the environment
-
Determine installed SurveyJS versionCheck package.json, composer.json, or the surveyjs library files for version information; compare against any documented affected version rangeAffected if Running an affected version of SurveyJS with file upload capability
-
Verify file upload feature is enabledLocate SurveyJS configuration files or survey definitions that include file upload question types; check if the survey creator allows file upload questionsAffected if File upload questions are enabled in any survey definitions
-
Check uploaded file storage locationExamine the web server configuration and SurveyJS settings for the uploadDirectory or similar parameter; verify if uploaded files are stored within the webrootAffected if Uploaded files are stored in a publicly accessible webroot directory
-
Inspect file type validation configurationReview SurveyJS settings or custom server-side code for allowedFileTypes, fileTypeExtension, or similar restrictions; verify if a strict allowlist is implementedAffected if No file type restrictions exist or only client-side validation without server-side allowlist enforcement is in place
A user is affected if SurveyJS with file upload capability is running and uploaded files are stored in a web-accessible location without strict server-side allowlist validation.
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 allowlist-based file type validation using both file extension and magic bytes/content-type verification; store uploads outside web root and disable script execution permissions on upload directories.
- Consultation3.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 $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50427 — 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-50427 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