dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-9648

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The WP ULike Pro plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the WP_Ulike_Pro_File_Uploader class in all versions up to, and including, 1.9.3. This makes it possible for unauthenticated attackers to upload limited arbitrary files like .php2, .php6, .php7, .phps, .pht, .phtm, .pgif, .shtml, .phar, .inc, .hphp, .ctp, .module, .html, .svg on the affected site's server which may make make other attacks like Cross-Site Scripting possible. Only versions up to 1.8.7 were confirmed vulnerable, however, the earliest tested version for a patch we have access to is 1.9.4, so we are considering 1.9.4 the patched version.

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 confidence

The WP ULike Pro WordPress plugin contains an arbitrary file upload vulnerability in the WP_Ulike_Pro_File_Uploader class. Insufficient file type validation allows unauthenticated attackers to upload files with dangerous extensions including multiple PHP variants (.php2, .php6, .php7, .phps, .pht, .phtm, .phar, .hphp, .ctp, .module), as well as .html and .svg files, which can enable secondary attacks such as Cross-Site Scripting.

MitigationUpdate the WP ULike Pro plugin to version 1.9.4 or later to patch the arbitrary file upload vulnerability. Until the update is applied, consider disabling the plugin or deploying a WAF rule to block malicious file upload requests.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WP ULike Pro plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or inspect the directory wp-content/plugins/ for a folder containing 'wp-ulike-pro' or similar
    Affected if The plugin is not found in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, view the plugin details to see the version number, or read the main plugin PHP file (e.g., wp-ulike-pro.php) and look for a Version: header comment
    Affected if The version is lower than 1.9.4 (for example, 1.9.3, 1.9.2, etc.)
  3. Verify file upload functionality is accessible
    The vulnerable class WP_Ulike_Pro_File_Uploader handles upload requests. Check if any frontend form, endpoint, or AJAX action related to file upload is active by examining plugin source code in includes/class-file-uploader.php or similar paths
    Affected if The upload functionality is enabled and accessible to unauthenticated users
  4. Confirm uploads directory is writable
    Check the wp-content/uploads directory permissions (via FTP, file manager, or ls -la command). Also check if the plugin creates a subdirectory for uploads
    Affected if The uploads directory is writable (permissions 755 or weaker with write for group/others)
  5. Inspect uploaded file extensions allowed
    If logs or a test environment are available, attempt a file upload with a double extension such as file.php.jpg or a forbidden extension like .php2, .phar, or .svg to see if the plugin accepts them. Examine the plugin's file type validation logic in the uploader class
    Affected if The plugin accepts dangerous extensions (.php variants, .html, .svg) without proper validation

A user is affected if the WP ULike Pro plugin is installed with a version lower than 1.9.4 and the file upload functionality is accessible, allowing dangerous file types to be uploaded.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP ULike Pro plugin to version 1.9.4 or later to patch the arbitrary file upload vulnerability. Until the update is applied, consider disabling the plugin or deploying a WAF rule to block malicious file upload requests.

Recommended fix High confidence

WP ULike Pro version 1.9.4

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP ULike Pro in the plugin list
  4. Click 'Update Now' to update to version 1.9.4 or later, or manually upload version 1.9.4 if automatic update is unavailable
  5. Verify the plugin is running version 1.9.4 or higher after update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9648 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9648 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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