CVE-2026-53737
Description
Juicer plugin versions up to 1.12.18 are vulnerable to stored XSS, allowing attackers to execute scripts in an administrator's browser.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Juicer plugin versions up to 1.12.18 are vulnerable to stored XSS, allowing attackers to execute scripts in an administrator's browser.
Vulnerability
Juicer versions through 1.12.18 fail to properly escape remote feed API response fields before rendering them on the admin settings page. This vulnerability exists because user-controlled data from connected feed sources is not neutralized before being displayed. [2]
Exploitation
An attacker who controls the data from a connected feed can inject script. This script will execute in an administrator's browser when the Juicer admin settings page is loaded. No specific privileges are mentioned as required for the attacker, but control over feed data is necessary. [2]
Impact
Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of an administrator's browser session. This could lead to session hijacking, unauthorized administrative actions, or further compromise of the WordPress site. [2]
Mitigation
Juicer versions 1.12.19 and later contain a fix for this vulnerability. Users are advised to update to the latest version of the plugin. [2]
AI Insight generated on Jun 10, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2(expand)+ 1 more
- (no CPE)
- (no CPE)range: <=1.12.18
Package: https://wordpress.org/plugins/juicer
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.