Skip to content

Product

wordpress armember-membership vulnerabilities

22 published CVES affecting wordpress armember-membership, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
22
Critical
4
High
8
Medium
10
Low
0
Unscored
0
CISA KEV
0

Latest wordpress armember-membership CVEs

Newest publication first

  1. MediumCVSS 5.3 EPSS 0.72%

    The ARMember plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.0.27 via the 'X-FILENAME' HTTP header. This makes it possible for unauthenticated attackers to upload and overwrite certain files (e.g., CSS) to directories outside the...

  2. MediumCVSS 6.3 EPSS 0.37%

    The The ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 4.0.51. This is due to the software allowing users to execute an action t...

  3. MediumCVSS 6.4 EPSS 1.1%

    The ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 4.0.37 due to insufficient input sanitization and output e...

  4. HighCVSS 8.8 EPSS 0.32%

    The ARMember plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.0.5. This is due to missing or incorrect nonce validation on the arm_check_user_cap function. This makes it possible for unauthenticated attackers to perform multiple...

  5. HighCVSS 8.1 EPSS 8.7%

    The ARMember WordPress plugin before 3.4.8 is vulnerable to account takeover (even the administrator) due to missing nonce and authorization checks in an AJAX action available to unauthenticated users, allowing them to change the password of arbitrary users by knowing their usern...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.