Zephyr Project Manager < 3.2.55 - Unauthorised AJAX Calls To Stored XSS
Description
Unauthenticated users can call AJAX actions in Zephyr Project Manager < 3.2.55, enabling stored XSS via lack of sanitization and CSRF.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Unauthenticated users can call AJAX actions in Zephyr Project Manager < 3.2.55, enabling stored XSS via lack of sanitization and CSRF.
Vulnerability
The Zephyr Project Manager WordPress plugin before version 3.2.55 lacks authorization and CSRF protection on all its AJAX actions, as reported in reference [1]. This allows unauthenticated attackers to invoke these actions directly or via cross-site request forgery. Additionally, the plugin does not sanitize or escape the input, enabling stored cross-site scripting (XSS).
Exploitation
An unauthenticated attacker can either send direct AJAX requests to the plugin's endpoints or trick an authenticated administrator into performing the request via CSRF. No special network position or user interaction is required beyond luring an admin if using CSRF. The attacker can then inject malicious JavaScript payloads that get stored and executed when an admin views the affected page.
Impact
Successful exploitation results in stored XSS, allowing the attacker to execute arbitrary JavaScript in the context of an administrator's session. This can lead to privilege escalation, data theft, or further compromise of the WordPress site.
Mitigation
The vulnerability is fixed in version 3.2.55 of the Zephyr Project Manager plugin, as indicated by the advisory [1]. Administrators should update to this version immediately. No known workarounds are available, and the issue is not listed on CISA's KEV.
AI Insight generated on May 27, 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: <=3.2.54
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
1- wpscan.com/vulnerability/82e01f95-81c2-46d8-898e-07b3b8a3f8c9mitrex_refsource_MISC
News mentions
0No linked articles in our index yet.