WordPress plugin · jch-optimize
Is JCH Optimize safe?
Safe on 6.1.1 or newer.
The current version, 6.1.1, is past every affected range on record (5 of 5 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 5
- High or critical
- 1
- Exploited
- none
- Current version
- 6.1.1
- Last updated
- Oct 19, 2026
- Active installs
- 4,000+
Every recorded flaw
- Sep 5, 2026JCH Optimize: Does not perform a capability check on one of its authenticated AJAX actions and lets the request chooseCVE-2026-84934 · fixed in 6.0.1 · reported by WPScanHigh 8
- Sep 5, 2026JCH Optimize: Does not properly restrict a directory path provided to one of its administrative image-browsing features to within the siteCVE-2025-15693 · fixed in 5.0.1 · reported by WPScanLow 2.7
- Jun 9, 2024JCH Optimize: Broken Access ControlCVE-2024-30481 · affects up to 4.0.0 · reported by PatchstackMedium 6.5
- May 16, 2024JCH Optimize: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVE-2024-34808 · affects up to 4.2.0 · reported by PatchstackMedium 4.3
- May 6, 2023Auth.CVE-2023-25491 · fixed in 3.2.3 · reported by PatchstackMedium 5.9
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.