Security readout for executives and security teams
Plain-English summary
WP Prayer for WordPress through version 1.6.5 can let an attacker change plugin settings or trigger a data export if they convince a logged-in site administrator to follow a forged request. This is not a direct takeover issue, but it can affect site integrity and operational trust.
Executive priority
Treat this as a moderate WordPress hygiene issue. It should be remediated during normal patch cycles, faster for public sites with many administrators or high-risk admin workflows. It is not supported as actively exploited in the provided evidence.
Technical view
CVE-2021-4412 is a CSRF weakness in WP Prayer save() and export() functions caused by missing or incorrect nonce validation. The reported impact is unauthenticated forged requests that rely on administrator interaction. CVSS 3.1 is 4.3, with network access, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is limited to WordPress sites using the WP Prayer plugin at versions up to and including 1.6.5. Sites without the plugin, or with a vendor-confirmed fixed version, are not indicated as affected by the provided sources.
Exploitation context
The provided bundle does not state active exploitation, and KEV status is false. Practical abuse requires social engineering a site administrator into taking an action while authenticated. The documented effects are plugin setting changes and triggering a data export.
Researcher notes
The key research point is CSRF protection on save() and export(). Evidence names missing or incorrect nonce validation, but the bundle does not provide exploit details, observed abuse, or a clearly named fixed version. Validate against vendor source history before closing remediation.
Mitigation direction
- Inventory WordPress sites for WP Prayer and record installed versions.
- Review vendor, WordPress.org, or plugin Trac guidance for the fixed release.
- Update WP Prayer if a vendor-confirmed patched version is available.
- Disable or replace the plugin if no trustworthy fix is available.
- Limit administrator sessions and access to trusted management networks where feasible.
Validation and detection
- Confirm whether WP Prayer is installed on each WordPress instance.
- Check whether installed versions are at or below 1.6.5.
- Review plugin changelog or Trac for nonce validation changes in save and export flows.
- Verify administrative requests require valid nonces and appropriate capability checks.
- Review logs for unexpected plugin setting changes or export activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-4412 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/a7efbdb1-989f-4171-ab55-aff66014337a?source=cveCVE reference
- https://blog.nintechnet.com/25-wordpress-plugins-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/more-wordpress-plugins-and-themes-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-3/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-2/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-1/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-5/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-4/CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2543740%40wp-prayer&new=2543740%40wp-prayer&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.