# CVE-2021-24836: Temporary Login Without Password < 1.7.1 - Subscriber+ Plugin's Settings Update

> Any logged-in user can modify plugin settings due to missing authorization and CSRF checks, potentially compromising site security.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-x8f8-g3c4-95m3

## What is CVE-2021-24836?

CVE-2021-24836 is a medium-severity missing authorization vulnerability in Unknown Temporary Login Without Password, published on 13 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Temporary Login Without Password WordPress plugin before 1.7.1 does not have authorisation and CSRF checks when updating its settings, which could allows any logged-in users, such as subscribers to update them

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-24836?

It affects 1 product.


Products: Storeapps Temporary Login Without Password.

## How do I fix CVE-2021-24836?

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

## Is CVE-2021-24836 being exploited?

There is no known exploitation of CVE-2021-24836 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24836 and fix it if it is affected.

What it is: CVE-2021-24836 is a medium-severity missing authorization vulnerability in Unknown Temporary Login Without Password, published on 13 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24836 in the wild and no public exploit code.

Affected product: Unknown Temporary Login Without Password. 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-2021-24836/ (Markdown: https://insights.sbomify.com/CVE-2021-24836/index.md)
```

## Sources

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

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