Juicer.io · Security record
Is Juicer.io safe?
One known vulnerability affects the current version (1.13.0), and it has no fix yet.
Checked 2 days ago against the WPVulnerability database, for version 1.13.0.
How it’s looked after
- Last release
- Sep 10, 2026 (1 month ago)
- Releases in the last year
- 3
- Tested up to
- WordPress 7.0.8
- Active installs
- 8K+
2 known vulnerabilities
- 2 medium
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20231
- 20261
Every known vulnerability in Juicer.io
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2026-53737 · Jun 10, 2026 · CVE
Fixed in 1.11 · CVE-2023-0172 · Jan 25, 2023 · Wordfence
Questions about Juicer.io’s security
Is Juicer.io safe to use?
Yes: 1 known vulnerability affects version 1.13.0, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Juicer.io have known security vulnerabilities?
Yes: 1 known vulnerability affects version 1.13.0, according to WPVulnerability’s database.
Is Juicer.io still maintained?
Yes. Its last release was 1 month ago. No support threads were opened in the last two months.
Is Juicer.io compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.