CVE-2024-52375
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 Arttia Creative Datasets Manager by Arttia Creative datasets-manager-by-arttia-creative.This issue affects Datasets Manager by Arttia Creative: from n/a through <= 1.5.
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 confidenceThis is an unrestricted file upload vulnerability in the Arttia Creative Datasets Manager plugin (versions up to 1.5). The plugin lacks proper validation on uploaded files, allowing attackers to upload dangerous file types (e.g., PHP scripts, web shells) that could lead to remote code execution on the affected server.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm plugin installationLocate the Arttia Creative Datasets Manager plugin in your CMS/plugin directory or check your site's plugin list for 'Arttia Creative Datasets Manager'Affected if The plugin is not installed or has been removed entirely
-
Identify installed versionCheck the plugin's version number in your CMS plugin management interface, readme file, or version metadata within the plugin filesAffected if Unable to determine the version or version is unknown/unpatched
-
Verify file upload feature is accessibleCheck if the file upload functionality in the Datasets Manager is enabled and accessible to users (even low-privileged users)Affected if File upload functionality is exposed and usable
-
Inspect upload endpoint configurationExamine the plugin's PHP files handling uploads, looking for file type/mime type validation logic before the move_uploaded_file() or similar file handling functionsAffected if No server-side file type validation is present or validation can be bypassed
-
Check uploaded file storage locationVerify where uploaded files are stored - if they remain in web-accessible directories with their original extensions intactAffected if Files are stored within web root without renaming or outside accessible execution restrictions
You are affected if the Arttia Creative Datasets Manager plugin is installed with its file upload feature enabled and lacks proper server-side file type validation, allowing execution-capable files to be stored in web-accessible locations.
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, sanitize file extensions and MIME types, store uploads outside the web root or with execute permissions removed, and add malware scanning for uploaded content.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52375 — 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-52375 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