Email settings modification via missing CSRF check
Published May 15, 2024 · Updated Jan 9, 2026
CSRF in Go Prayer WP Prayer 2.0.9 and earlier allows remote attackers to alter email settings through a forged administrator request. The wpe_manage_email_settings page accepts posted email configuration fields and a save operation without a CSRF token check. Exploitation requires a logged-in administrator to open attacker-controlled HTML, after which the browser submits the unauthorized settings change.
Summary
What happened
CSRF in Go Prayer WP Prayer 2.0.9 and earlier allows remote attackers to alter email settings through a forged administrator request. The wpe_manage_email_settings page accepts posted email configuration fields and a save operation without a CSRF token check. Exploitation requires a logged-in administrator to open attacker-controlled HTML, after which the browser submits the unauthorized settings change.
The record
- CVE
- CVE-2024-3406
- Published
- May 15, 2024
- Updated
- Jan 9, 2026
- Vendor
- Go Prayer
- Product
- WP Prayer
- Classifications
- CWE-352, CAPEC-62, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2024CVE publishedPublication date reported by the CVE source.
- Jan 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.0.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan forged email-settings request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo