CVE-2024-3966: The Pray For Me WordPress plugin through 1.0.4 does not sanitise and escape some parameters, which could unaut

Q: How do I fix CVE-2024-3966?

pray for me: upgrade to newer than 1.0.4. Exact commands for each OS are on this page.

Q: Is CVE-2024-3966 being exploited?

CVE-2024-3966 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-3966 affect?

CVE-2024-3966 affects pray for me. Severity is medium (CVSS 6.1). The Pray For Me WordPress plugin through 1.0.4 does not sanitise and escape some parameters, which could unauthenticated visitors to perform Cross-Site Scripting attacks that trigger when an admin visits the Prayer Requests in the WP Admin

Q: How urgent is CVE-2024-3966?

Priority 33/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2024-3966 is a medium-severity flaw (CVSS 6.1) affecting pray for me. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Pray For Me WordPress plugin through 1.0.4 does not sanitise and escape some parameters, which could unauthenticated visitors to perform Cross-Site Scripting attacks that trigger when an admin visits the Prayer Requests in the WP Admin

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-06-14
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: projectcaruso

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-14 06:15 UTCPublished CVE record published
2026-06-17 07:45 UTCUpdated Record last modified

projectcaruso pray for me UPGRADE

Affected: <= 1.0.4

Fixed in: newer than 1.0.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pray-for-me || rpm -q pray-for-me || pray-for-me --version

2. UPGRADE to newer than 1.0.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pray-for-me

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pray-for-me

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-3966?

pray for me: upgrade to newer than 1.0.4. Exact commands for each OS are on this page.

Is CVE-2024-3966 being exploited?

CVE-2024-3966 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-3966 affect?

CVE-2024-3966 affects pray for me. Severity is medium (CVSS 6.1). The Pray For Me WordPress plugin through 1.0.4 does not sanitise and escape some parameters, which could unauthenticated visitors to perform Cross-Site Scripting attacks that trigger when an admin visits the Prayer Requests in the WP Admin

How urgent is CVE-2024-3966?

Priority 33/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-3965 MEDIUM 5.4 UPGRADE The Pray For Me WordPress plugin through 1.0.4 does not have CSRF check in place when updating its settings, w

References

← Back to latest CVEs