CVE-2024-54285
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 SeedProd LLC SeedProd Pro allows Upload a Web Shell to a Web Server.This issue affects SeedProd Pro: from n/a through 6.18.10.
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 confidenceThe SeedProd Pro WordPress plugin versions up to 6.18.10 contain an unrestricted file upload vulnerability allowing attackers to upload malicious PHP files (web shells) to the web server. This grants remote code execution capabilities and complete server compromise.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 SeedProd Pro plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect wp-content/plugins/seedprod-pro folder via file manager/FTPAffected if SeedProd Pro plugin is present on the WordPress site
-
Identify installed versionCheck the plugin version in the plugin header comment within the main plugin file (seedprod-pro.php) or view the plugin details page in WordPress admin under Plugins > Installed PluginsAffected if Version listed is 6.18.10 or any earlier version
-
Check if file upload functionality is enabledReview SeedProd Pro plugin settings, particularly any landing page builder features that accept file uploads or user submissions. Look in Settings > SeedProd Pro or any submenu for upload-related optionsAffected if File upload or submission forms are active and publicly accessible without additional access controls
-
Inspect upload directories for suspicious filesExamine wp-content/uploads/ and subdirectories for unfamiliar PHP files, shell scripts, or files with double extensions (e.g., .php.jpg). Use file system search or FTP to list and review recent filesAffected if Unexpected PHP files, web shells, or executable scripts exist in upload directories, especially with creation dates after plugin installation or update
The environment is affected if SeedProd Pro plugin is installed with version 6.18.10 or lower and file upload features are accessible to users or unauthenticated attackers.
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 dataUpgrade SeedProd Pro to version 6.18.11 or later which includes proper file type validation and restricts uploaded files to safe types (images, documents) while blocking executable script extensions.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54285 — 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-54285 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