CVE-2025-50848
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 file upload vulnerability was discovered in CS Cart 4.18.3, allows attackers to execute arbitrary code. CS Cart 4.18.3 allows unrestricted upload of HTML files, which are rendered directly in the browser when accessed. This allows an attacker to upload a crafted HTML file containing malicious content, such as a fake login form for credential harvesting or scripts for Cross-Site Scripting (XSS) attacks. Since the content is served from a trusted domain, it significantly increases the likelihood of successful phishing or script execution against other users.
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 confidenceCS Cart 4.18.3 contains an unrestricted file upload vulnerability where HTML files can be uploaded and served from the trusted domain. Since these uploaded HTML files are rendered directly by the browser, attackers can embed malicious content such as credential harvesting forms or XSS payloads, exploiting the trusted domain context to enhance phishing and script execution attacks.
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= 4.18.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm CS Cart versionLocate the installation directory and check the version file or admin panel. Common paths include /app/version.php or checking the admin dashboard 'About' section.Affected if The installed version is exactly 4.18.3
-
Identify file upload functionalityNavigate to the admin panel and locate sections that handle file uploads: product images, product files, attachments, or theme editor uploads. Check the file upload forms and their handling code.Affected if File upload functionality exists and accepts user-submitted files
-
Examine allowed file type validationInspect the upload handler code (typically in app/Tygh/Upload.php or similar) to see which file extensions are permitted. Look for whether .html, .htm, or other HTML-related extensions are in the allowed list.Affected if HTML file extensions (.html, .htm) are permitted in the upload whitelist or validation is missing
-
Check uploaded file serving behaviorUpload a benign HTML test file (e.g., <html><body>test</body></html>) through the identified upload mechanism. Then attempt to access the uploaded file directly via browser and check the response headers.Affected if The uploaded HTML file is accessible via URL and served with Content-Disposition: inline (or missing Content-Disposition header), causing it to render in the browser rather than download
-
Verify Content-Security-Policy headersUse browser dev tools or a command like 'curl -I <url>' to inspect HTTP response headers when accessing the storefront or uploaded files. Check for CSP headers that would block inline script execution.Affected if No Content-Security-Policy header is present, or CSP allows 'unsafe-inline' for script sources, enabling XSS execution from uploaded HTML
You are affected if running CS Cart exactly version 4.18.3 AND the file upload feature accepts and serves HTML files inline from the trusted domain without restrictive CSP headers.
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 on upload, rename uploaded files to remove extensions, store files outside the webroot or serve them with Content-Disposition: attachment headers to prevent inline rendering, and add Content-Security-Policy headers to restrict script execution.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50848 — 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-2025-50848 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