# CVE-2022-1903: ARMember < 3.4.8 - Unauthenticated Admin Account Takeover

> Unauthenticated attackers can take over any user account, including administrators, by exploiting missing authorization checks in an AJAX action.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-84p8-fx26-f9cw

## What is CVE-2022-1903?

CVE-2022-1903 is a high-severity missing authorization vulnerability in Unknown ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup, published on 27 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 username

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-1903?

It affects 1 product.


Products: Armemberplugin Armember.

## How do I fix CVE-2022-1903?

No fix has been published for CVE-2022-1903 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-1903 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1903 exists.

Public exploit code:

- ARMember < 3.4.8 - Unauthenticated Admin Account Takeover (github_poc): https://github.com/biulove0x/CVE-2022-1903
- ARMember < 3.4.8 - Unauthenticated Admin Account Takeover (nuclei): http/cves/2022/CVE-2022-1903.yaml

## Other vulnerabilities in Unknown ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup

- [CVE-2022-42888](https://insights.sbomify.com/CVE-2022-42888/): WordPress ARMember Plugin <= 5.5.1 is vulnerable to Privilege Escalation (critical 9.8)
- [CVE-2023-3011](https://insights.sbomify.com/CVE-2023-3011/): ARMember <= 4.0.5 - Cross-Site Request Forgery (medium 6.5)
- [CVE-2022-47421](https://insights.sbomify.com/CVE-2022-47421/): WordPress ARMember (free) and ARMember (premium) plugins - vulnerable to Auth. Stored Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2023-3996](https://insights.sbomify.com/CVE-2023-3996/): ARMember Lite - Membership Plugin <= 4.0.16 - Authenticated (Administrator+) Stored Cross-Site Scripting (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1903 and fix it if it is affected.

What it is: CVE-2022-1903 is a high-severity missing authorization vulnerability in Unknown ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup, published on 27 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1903 exists.

Affected product: Unknown ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1903/ (Markdown: https://insights.sbomify.com/CVE-2022-1903/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1903
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1903
- OSV: https://osv.dev/vulnerability/CVE-2022-1903

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1903/
Summaries are generated and may contain mistakes; the official description above is the record.