WP-Optimize vulnerability history, and the four tools one version number covers
WP-Optimize is a page cache, an image compressor, a database cleaner and a minifier in one plugin, and titles in its history carry the wording Subscriber+, Author+ and Admin+.
Read each record by its fields, then read each screen.
On this page
WP-Optimize vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 5 records for WP-Optimize. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 4.5.3
Worked out from data retrieved on .
Every affected range listed in this source for WP-Optimize ends before version 4.5.3.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
WP-Optimize <= 4.5.2 - Authenticated (Author+) Arbitrary File Deletion via 'original-file' Post Meta
- Published:
- Last updated:
- Severity:
- High (CVSS 8.1)
- CVE:
- CVE-2026-7252
Affected versions- All versions up to and including 4.5.2
Patched versions: 4.5.3
Update to at least version 4.5.3.
WP-Optimize <= 4.5.0 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Update and Image Manipulation
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.4)
- CVE:
- CVE-2026-2712
Affected versions- All versions up to and including 4.5.0
Patched versions: 4.5.1
Update to at least version 4.5.1.
WP-Optimize <= 4.1.1 - Authenticated (Admin+) SQL Injection
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.9)
- CVE:
- CVE-2025-3951
Affected versions- All versions up to and including 4.1.1
Patched versions: 4.2.0
Update to at least version 4.2.0.
WP-Optimize <= 3.2.12 & SrbTransLatin <= 2.4 - Stored/Reflected Cross-Site Scripting via Third Party Library
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2023-1119
Affected versions- All versions before 3.2.13
Patched versions: 3.2.13
Update to at least version 3.2.13.
WP-Optimize <= 3.2.11 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
Affected versions- All versions up to and including 3.2.11
Patched versions: 3.2.12
Update to at least version 3.2.12.
Check WP-Optimize on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
Four tools in one plugin: what WP-Optimize touches on a site
WP-Optimize is published on WordPress.org by David Anderson / Team Updraft, and its listing gives it four jobs: caching the site, compressing images, cleaning the database and minifying HTML, JavaScript and CSS.
The cache, by the listing's FAQ, saves the page computed by WordPress on the disk and serves it before WordPress is loaded.
Record titles in the history carry the access wording (Subscriber+), (Author+) and (Admin+). By WordPress's documentation a Subscriber holds only the read capability, and an Author can publish its own posts and holds upload_files. For a (Subscriber+) title, read Settings > General too: when Anyone can register is ticked, anyone can register an account, and New User Default Role sets the role it receives.
Reading WP-Optimize vulnerabilities: a title's access wording, then the version fields
For WP-Optimize, match the installed version to each record's affected range and patched versions field, not to the version a title carries.
- CVE-2026-2712, whose title ends Missing Authorization to Authenticated (Subscriber+) Plugin Settings Update and Image Manipulation. Affected: all versions up to and including 4.5.0. Patched: 4.5.1.
- CVE-2026-7252, whose title ends Authenticated (Author+) Arbitrary File Deletion via 'original-file' Post Meta. Affected: all versions up to and including 4.5.2. Patched: 4.5.3.
- CVE-2025-3951, whose title ends Authenticated (Admin+) SQL Injection. Affected: all versions up to and including 4.1.1. Patched: 4.2.0.
- CVE-2023-1119, titled WP-Optimize <= 3.2.12 & SrbTransLatin <= 2.4 - Stored/Reflected Cross-Site Scripting via Third Party Library. Affected: all versions before 3.2.13. Patched: 3.2.13.
- A record with no CVE id, matched by its title, which ends Cross-Site Request Forgery. Affected: all versions up to and including 3.2.11. Patched: 3.2.12.
The 3.2 records, and a second place to read
A patched version answers one record, not the history: the record with no CVE id whose title ends Cross-Site Request Forgery lists 3.2.12 in its patched versions field, and 3.2.12 falls inside the range of CVE-2023-1119, all versions before 3.2.13. That CVE's title carries a second name, SrbTransLatin <= 2.4, so match on the fields.
The changelog on the plugin's WordPress.org listing has marked entries with the word SECURITY, and a fix it describes may have no record on this page, so read it before relying on the update guidance at the top of the history.
Carrying out the WP-Optimize checks, screen by screen
Every step is a read.
WP-Optimize puts action buttons beside its settings, such as Purge cache in the cache screen's text and Run all selected optimizations in the vendor's database guide: press none and save nothing.
The WordPress Plugins screen gives each plugin's version number in its Description column. Write down every WP-Optimize row, the version and name each gives, whether it is active and what its Automatic update column shows. The vendor's install guide has the free plugin installed from Plugins > Add New Plugin and WP-Optimize Premium uploaded as a file, and says a free version already on the site is automatically deactivated.
The vendor's caching guide starts at WP-Optimize > Cache and says to click the Cache tab; its site speed tutorial puts Enable page caching within a Page cache tab. Write down whether page caching is enabled, the Cache lifespan, and the option the plugin's text labels Serve cached pages to logged in users.
The plugin's text says to enable that option if you do not have user-specific or restricted content on your website, adding that it works only when the cache is preloaded, and the listing says to turn it on if content stays the same for logged in users, or to turn it on and exclude URLs where content does change, such as my account areas.
The caching guide says to tick it if you have user specific or restricted content. Where it is on and the site has accounts, put that first in your notes.
The guide puts exclusions on the Advanced settings tab: copy each list in full. Headings in the plugin's text include URLs to exclude from caching and Cookies which, if present, will prevent caching.
The vendor's database guide starts at WP-Optimize > Database. The plugin's text has a section headed Scheduled clean-up settings, where WP-Optimize has a tick box labelled Enable scheduled clean-up and optimization and a schedule type whose label gives Weekly as the default. Write down both, and which clean-ups the schedule runs.
Copy the general database settings: weeks of data to keep, post revisions to always keep, and whether a backup with UpdraftPlus is taken before scheduled runs. The plugin's text says that if the keep-weeks option is not active, all garbage data will be removed.
The vendor's image guide puts these settings at WP-Optimize > Images, with a choice of three compression levels. Write down the level, whether Automatically compress newly-added images is on, and, under Show advanced options, the Compression service.
The plugin's text says the feature is offered via the reSmush.it free API; the vendor's site speed tutorial calls reSmush.it an external service, names a second, Nitrosmush, and says reSmush.it is selected by default.
Note Backup original images: the plugin's text says the originals are stored alongside the compressed images.
The listing marks Cache purging permissions as Premium: selecting which user roles are allowed to purge the cache. On a Premium site, find that list of roles and copy it.
The plugin's general settings text has an option labelled Enable the caching menu in the admin bar, and a line in the listing's changelog mentions an admin bar cache menu for non-admin roles with cache purge permissions on the frontend. With each login you already hold, note whether the menu shows, and choose nothing from it.
The listing's FAQ says publishing or updating content clears the cache for that post or page, so list who holds Author, Editor and Administrator from the Role column of the Users screen. The changelog says cache purge operations are logged under uploads/wpo/logs: where those files exist, read them beside your list.
WP-Optimize security beyond the version check
A version inside an affected range shows that a known record covers that copy of WP-Optimize.
It does not show whether anyone used the flaw, which roles a Premium site lets purge the cache, or what was cached while pages were served to logged in users. Nor does it cover files beside the plugin: the listing's FAQ says the caching feature defines WP_CACHE in wp-config.php, needs access once to wp-content/advanced-cache.php and writes its cache settings to wp-content/wpo-cache.
A WordPress security audit tests the roles: it signs in with two accounts at subscriber level, replays requests captured from an administrator's plugin settings screens, here the WP-Optimize ones, and records whether each is refused.
Frequently asked questions
Each record carries its own range, and a patched version in one can sit inside the range of another: the record with no CVE id whose title ends Cross-Site Request Forgery lists 3.2.12, and CVE-2023-1119 covers all versions before 3.2.13. Check the installed version against every affected range in the history, then read the update guidance at the top of the history.
Set the version in the Description column of the Plugins screen beside the update guidance at the top of the history. WordPress displays an update notice there when a plugin hosted in its directory has a newer version. For one installed from a ZIP file, it says a notice appears only if the author includes a built-in updater, and the vendor's install guide says linking the site to your licences enables WP-Optimize Premium to receive automatic updates.
The records here are the ones the source data files under the slug wp-optimize, the free plugin's address on WordPress.org. Being filed there does not settle whether a record applies to Premium. The vendor's install guide says Premium is downloaded from your confirmation email or Account page and uploaded as a file, and that the free version does not have to be installed to run it. Record which edition a site runs and ask the vendor about any record you cannot place.
The listing's FAQ says WP-Optimize caching lets you cache products with plugins like WooCommerce or Easy Digital Downloads, or any e-commerce that uses DONOTCACHEPAGE to exclude sensitive pages from caching, and gives my account, cart or checkout pages as examples. A changelog line on the listing reads FIX: Prevent caching pages when a WooCommerce cart has content. The FAQ's test for any page is to view its source and scroll to the bottom for a line added by the cache, which it says a further service that minifies HTML, such as Cloudflare, may have removed.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 4 of the 5 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- WP-Optimize <= 4.5.2 - Authenticated (Author+) Arbitrary File Deletion via 'original-file' Post Meta (CVE-2026-7252)
- WP-Optimize <= 4.5.0 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Update and Image Manipulation (CVE-2026-2712)
- WP-Optimize <= 4.1.1 - Authenticated (Admin+) SQL Injection (CVE-2025-3951)
- WP-Optimize <= 3.2.12 & SrbTransLatin <= 2.4 - Stored/Reflected Cross-Site Scripting via Third Party Library (CVE-2023-1119)
- WP-Optimize <= 3.2.11 - Cross-Site Request Forgery