CVE-2024-49658
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 ecomerciar Woocommerce Custom Profile Picture woo-custom-profile-picture allows Upload a Web Shell to a Web Server.This issue affects Woocommerce Custom Profile Picture: from n/a through <= 1.0.
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 ecomerciar Woocommerce Custom Profile Picture plugin contains an unrestricted file upload vulnerability allowing attackers to upload arbitrary files including web shells. The plugin fails to validate file types or restrict dangerous extensions, enabling 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
- 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.
-
Verify plugin installationCheck for the 'woocommerce-custom-profile-picture' or 'ecomerciar' plugin directory in wp-content/plugins/ and list its filesAffected if The plugin directory exists in the WordPress plugins folder
-
Determine installed plugin versionOpen the main plugin PHP file or readme.txt in the plugin directory and locate the 'Version:' headerAffected if Version is present but cannot be confirmed as patched, or version is unknown/unlisted
-
Identify upload functionalitySearch the plugin directory for file upload-related functions: move_uploaded_file, wp_handle_upload, or form inputs with type='file'. Check for AJAX endpoints handling uploadsAffected if The plugin contains file upload handling code without proper validation checks
-
Check authentication on upload endpointsReview the plugin's PHP files for upload handlers and verify if they include capability checks (current_user_can) or nonce verification before processing uploadsAffected if Upload endpoints lack authentication, authorization, or nonce validation checks
-
Inspect file type validationExamine upload handler code for mime type validation, extension allowlisting, or file content validation (getimagesize, exif_read_data)Affected if No file type/extension validation exists, or validation can be bypassed easily
-
Verify upload directory configurationCheck wp-config.php and .htaccess for UPLOADS constant or custom upload path settings; determine if uploads are stored inside webrootAffected if Upload directory is within wp-content/uploads and accessible via web browser
If the plugin is installed and its upload functionality lacks proper file type validation and authentication, the environment is affected by this vulnerability.
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 (both MIME type and extension), store uploads outside webroot, disable script execution in upload directories, and add proper authentication checks for upload endpoints.
- Consultation2.0 h
- Implementation6.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 $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49658 — 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-49658 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