Image Optimizer <= 1.7.4 - Authenticated (Author+) Arbitrary File Deletion via Post Meta Field Injection
Impact
The Image Optimizer plugin for WordPress is vulnerable to arbitrary file deletion in versions up to and including 1.7.4. This is due to insufficient path validation in the Image_Backup::remove() function where backup file paths stored in post meta are used directly in file deletion operations without verifying they are within the uploads directory. The plugin stores backup file paths in the image_optimizer_metadata post meta field and trusts these paths completely when deleting backups on the delete_attachment hook. An authenticated attacker with Author-level access can edit the…
Source excerpt · WordfenceAffected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
elemntor · Image Optimizer – Compress Images and Convert to WebP or AVIF
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 0 through 1.7.4 (inclusive) | affected |
Original source description
The Image Optimizer plugin for WordPress is vulnerable to arbitrary file deletion in versions up to and including 1.7.4. This is due to insufficient path validation in the Image_Backup::remove() function where backup file paths stored in post meta are used directly in file deletion operations without verifying they are within the uploads directory. The plugin stores backup file paths in the image_optimizer_metadata post meta field and trusts these paths completely when deleting backups on the delete_attachment hook. An authenticated attacker with Author-level access can edit the image_optimizer_metadata post meta on their own attachments via WordPress's Custom Fields interface, injecting arbitrary absolute file paths into the backups array. When the attacker subsequently deletes the attachment, the plugin calls File_System::delete() on each path without validation. This makes it possible for authenticated attackers, with Author-level access and above, to delete arbitrary files on the server within the web server's filesystem permissions, potentially leading to denial of service, data loss, or security degradation.
References
- Security advisory www.wordfence.com/threat-intel/vulnerabilities/id/a1a00374-e9d6-46f9-a28c-cb7768505787
- Source reference plugins.trac.wordpress.org/browser/image-optimization/trunk/classes/image/image-backup.php
- Source reference plugins.trac.wordpress.org/browser/image-optimization/tags/1.7.3/classes/image/image-backup.php
- Source reference plugins.trac.wordpress.org/browser/image-optimization/trunk/modules/backups/components/handle-backups-removing.php
- Source reference plugins.trac.wordpress.org/browser/image-optimization/tags/1.7.3/modules/backups/components/handle-backups-removing.php
- Source reference plugins.trac.wordpress.org/browser/image-optimization/trunk/classes/image/image-meta.php
- Source reference plugins.trac.wordpress.org/browser/image-optimization/tags/1.7.3/classes/image/image-meta.php
- Patch plugins.trac.wordpress.org/changeset
- Security advisory research.cleantalk.org/cve-2026-5821