# CVE-2024-1290: Formidable Registration < 2.12 - Contributor+ Arbitrary User Password Reset To Account Takeover

> Contributors can exploit shortcode rendering to leak password reset URLs and take over arbitrary user accounts in the User Registration plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 11 Mar 2024
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-hgjm-23r8-g35c

## What is CVE-2024-1290?

CVE-2024-1290 is a medium-severity missing authorization vulnerability in Unknown User Registration, published on 11 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The User Registration WordPress plugin before 2.12 does not prevent users with at least the contributor role from rendering sensitive shortcodes, allowing them to generate, and leak, valid password reset URLs, which they can use to take over any accounts.

## Which versions are affected by CVE-2024-1290?

It affects 1 product.


Products: Strategy11 User Registration Forms.

## How do I fix CVE-2024-1290?

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

## Is CVE-2024-1290 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1290 and fix it if it is affected.

What it is: CVE-2024-1290 is a medium-severity missing authorization vulnerability in Unknown User Registration, published on 11 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1290 in the wild and no public exploit code.

Affected product: Unknown User Registration. 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-2024-1290/ (Markdown: https://insights.sbomify.com/CVE-2024-1290/index.md)
```

## Sources

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

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