Skip to content
Web

CVE-2026-13352

8.8
High
EPSS 1%Patch availableJul 17, 2026

Authenticated arbitrary file upload in ProfilePress plugin enabling potential RCE.

common questions

Is CVE-2026-13352 being exploited?

Not confirmed. CVE-2026-13352 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.1% probability of exploitation in the next 30 days.

How severe is CVE-2026-13352?

CVE-2026-13352 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-13352?

Yes. A fix has been recorded for CVE-2026-13352. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-13352 affect?

CVE-2026-13352 affects ProfilePress (Paid Membership Plugin) for WordPress <= 4.16.18, WordPress sites with ProfilePress installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-13352?

Update ProfilePress to patched version; restrict upload rights and block executable MIME types

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ProfilePress (Paid Membership Plugin) for WordPress <= 4.16.18WordPress sites with ProfilePress installed
impact

Author-level users can upload executable files (.exe/.apk/.msi) site-wide via MIME allowlist expansion, potentially leading to remote code execution.

action required

Immediate action required

affected versions
properfraction Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress
  • affected<= 4.16.18

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free