CVE-2022-47424 is a medium severity (CVSS 5.4) cross site request forgery flaw in the ARMember membership plugin through 4.0.5, and in ARMember Premium before 6.7.1. A logged in user can be tricked into an unwanted action. Update the plugin, and move Premium to 6.7.1 or later.
What's affected
The record lists two products. ARMember, the free edition, is affected from the earliest release through 4.0.5. ARMember Premium is affected before 6.7.1, which makes 6.7.1 the fixed release for that edition. I could not confirm a fixed version for the free edition from a source I could read.
The NVD record was published on 19 November 2024. The Patchstack entry cited by the record covers ARMember 4.0.5.
How to check if you're exposed
In the WordPress admin, open Plugins and read the version shown under ARMember. With WP-CLI you can run wp plugin list --fields=name,status,version and look for the entry. Check inactive plugins too, since a deactivated plugin still sits on disk.
What to do now
- Update ARMember to the latest release, and update ARMember Premium to 6.7.1 or later.
- If an update is not available yet, deactivate and delete the plugin, or restrict access to it while you wait. Do not leave a vulnerable copy installed but switched off.
- Review your site for changes you did not make, such as new accounts, altered content or unexpected files, and rotate credentials if anything looks wrong.
- Add the plugin to your inventory so the next advisory for it reaches you without a manual search.
Why it matters
CWE-352 is cross site request forgery. The plugin accepts a state changing request without confirming that the person meant to send it, so another web page can cause a logged in user's browser to send it. The usual defense is a per request nonce that the server verifies.
The record needs user interaction, low integrity and low availability impact. A membership plugin often runs with administrators logged in, which is why administrators should avoid browsing other sites while signed in to the dashboard. KEV is false.
If your site runs a membership plugin, keep a record of which edition you use. The free and premium editions of ARMember have different version numbers, as the advisory ranges above show, and a version that is fixed in one is not necessarily the fixed version in the other.
Quick check
Which versions are affected?
ARMember through 4.0.5, and ARMember Premium before 6.7.1.
Does the attacker need to log in?
No, but the victim does. The attacker relies on a logged in user taking an action.
Sources
You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.
Last reviewed: 19 October 2026.