WP images upload on piclect Plugin Vulnerability (CVE-2026-84171)

On this page

Security Alert Summary

The WP images upload on piclect WordPress plugin (versions up to and including 1.0) fails to validate uploaded file names and types before writing them to a publicly accessible directory. This allows unauthenticated attackers to upload arbitrary files, which can lead to execution of arbitrary code on the server.


CVE Details

  • CVE ID: CVE-2026-84171
  • Affected component: WP images upload on piclect
  • Affected versions: Versions up to and including 1.0
  • Published: September 12, 2026 06:16:27 AM UTC
  • Last modified: September 12, 2026 04:16:41 PM UTC
  • CVSS v3.1: Base score 9.8, severity CRITICAL, vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Authentication / privileges / user interaction: No authentication required; privileges required: none; user interaction: none
  • Primary impact: Confidentiality: High; Integrity: High; Availability: High
  • Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)
  • SSVC summary: exploitation: none; automatable: yes; technical impact: total

Technical Details

The plugin fails to validate the name or MIME/type of uploaded files before writing them into a publicly accessible directory. Because uploads are not checked for allowed extensions or content type, an attacker can upload files that the server may execute (for example, executable scripts) or serve to visitors. The lack of validation on file names and types is the root cause.

The reported impact is direct: unauthenticated attackers can upload arbitrary files and achieve execution of arbitrary code on the server where the plugin writes uploaded files.


How This Could Impact Your Website

On a multiuser WordPress site, a site owner or administrator may rely on the plugin to let contributors or external contractors upload images. If the plugin accepts uploads without validating file names or types, an unauthenticated attacker could place a malicious file in a public folder. Practically, this could lead to:

  • Exposure of internal user data if an attacker leverages uploaded files to access other parts of the site.
  • Increased risk of targeted phishing or social engineering if attacker-controlled content is served from the site and used to impersonate staff or contractors.
  • Execution of arbitrary code on the server, potentially allowing modification of site content or installation of backdoors accessible by external actors.

If youre unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributors and any untrusted uploaders.
  • Enforce strong passwords and two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins that increase attack surface.
  • Monitor site activity and server logs for unusual upload behavior or unexpected file creation in public directories.

If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References