CVE-2026-120514 · Other
NO FIX YET
The Zephyr Project Manager WordPress plugin does not sanitize the zpm_profile_picture parameter, so a subscriber-level account can store a script in their profile. When an administrator later views the affected avatar field, the script runs in that administrator's browser session.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Zephyr Project Manager plugin through version 3.3.209 where subscribers can register or log in and edit profiles. The attacker needs a subscriber-level account and an administrator must view the injected content, so sites without open registration or with the plugin removed can skip it.
Not affected if no-subscriber-accounts, plugin-not-installed
Who cares wordpress, zephyr-project-manager
3.3.209 or lowerNo fix yet, per the sources.
The Zephyr Project Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'zpm_profile_picture' parameter in all versions up to, and including, 3.3.209 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is stored in the subscriber's own Zephyr profile and fires in any Administrator's browser session the first time the autocomplete mention lookup renders the avatar field, requiring no additional configuration beyond the plugin's default access_roles setting. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.