ProfilePress executes attacker-supplied shortcodes from public profile fields
ProfilePress before 4.17.1 does not strip shortcodes from two profile fields before rendering them on public pages. An unauthenticated attacker can store a shortcode in those fields; when the affected page is rendered, WordPress executes it and discloses a chosen user's email address, login name and registration date.
- Component
- ProfilePress
- Plugin slug
profilepress- Affected
- < 4.17.1
- Safe version
4.17.1- Published
- Aug 21, 2026
This CVE was published Aug 21, 2026 and is one of 26 known issues for this plugin.
Update, patch or deactivate.
Update ProfilePress to 4.17.1 or later. Review public profile data for unexpected shortcode syntax and assess whether user email addresses, login names or registration dates may have been exposed.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The ProfilePress WordPress plugin before 4.17.1 does not strip shortcodes from two of its profile fields before rendering them on public pages, allowing unauthenticated attackers to store shortcodes that are then executed when the page is viewed, disclosing a chosen user's email address, login and registration date.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N