# CVE-2021-4412: WP Prayer <= 1.6.5 - Cross-Site Request Forgery Bypass

> Unauthenticated attackers can trick administrators into modifying plugin settings or triggering data exports via forged requests.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jul 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-45fv-hg56-qgcj

## What is CVE-2021-4412?

CVE-2021-4412 is a medium-severity vulnerability in abrg WP Prayer, published on 12 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WP Prayer plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.6.5. This is due to missing or incorrect nonce validation on the save() and export() functions. This makes it possible for unauthenticated attackers to save plugin settings and trigger a data export via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Goprayer Wp Prayer.

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

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

## Is CVE-2021-4412 being exploited?

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

## Other vulnerabilities in abrg WP Prayer

- [CVE-2024-3406](https://insights.sbomify.com/CVE-2024-3406/): WP Prayer <= 2.0.9 - Email Settings Update via CSRF (high 8.8)
- [CVE-2024-3405](https://insights.sbomify.com/CVE-2024-3405/): WP Prayer <= 2.0.9 - Settings Update via CSRF (high 7.6)
- [CVE-2023-25705](https://insights.sbomify.com/CVE-2023-25705/): WordPress WP Prayer Plugin <= 1.9.6 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2021-24313](https://insights.sbomify.com/CVE-2021-24313/): WP Prayer < 1.6.2 - Authenticated Stored Cross-Site Scripting (XSS) (medium 5.4)
- [CVE-2024-3407](https://insights.sbomify.com/CVE-2024-3407/): WP Prayer <= 2.0.9 - Arbitrary Prayer Deletion via CSRF (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-4412 is a medium-severity vulnerability in abrg WP Prayer, published on 12 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-4412 in the wild and no public exploit code.

Affected product: abrg WP Prayer. 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-4412/ (Markdown: https://insights.sbomify.com/CVE-2021-4412/index.md)
```

## Sources

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

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