CVE-2024-25802
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 · uneditedSKINsoft S-Museum 7.02.3 allows Unrestricted File Upload via the Add Media function. Unlike in CVE-2024-25801, the attack payload is the file content.
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 · high confidenceSKINsoft S-Museum 7.02.3 contains an unrestricted file upload vulnerability in the Add Media function. The application does not properly validate uploaded file content, allowing attackers to upload malicious files (such as web shells) that could lead to remote code execution on the server.
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= 7.02.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Confirm S-Museum versionAccess the application's admin panel or check the installation directory for version information. Typically found in about.php, version.txt, or the admin dashboard.Affected if The installed version is exactly 7.02.3 (the only affected version listed)
-
Locate the Add Media functionNavigate to the administrative interface and identify the Add Media or file upload functionality. This is typically found under Media, Assets, or Upload sections in the admin panel.Affected if The Add Media function exists and is accessible to the user (attacker)
-
Identify upload directoryCheck the application's configuration files (config.php, settings.php) or web server config for the upload path. Common paths include /uploads/, /media/, or /assets/.Affected if Uploads are stored within the web root without restrictions
-
Verify file type validationExamine the application's source code or proxy the upload request to inspect how the server validates file uploads. Check for magic byte validation, extension whitelist, or Content-Type header checks.Affected if No server-side validation exists or validation can be bypassed (e.g., allows .php, .exe, .asp files)
-
Check for existing malicious uploadsList all files in the upload directories. Look for suspicious extensions (php, phtml, asp, aspx, jsp, exe, sh) or files with double extensions.Affected if Unexpected script files or web shells are present in upload directories
A user is affected if they run S-Museum version 7.02.3 with the Add Media function accessible and without proper file validation on uploads.
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 validation including magic byte verification, whitelist allowed file types, store uploads outside the web root or on isolated storage, and disable script execution in upload directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25802 — 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-25802 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