CVE-2025-22590
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in mmrs151 Prayer Times Anywhere prayer-times-anywhere allows Stored XSS.This issue affects Prayer Times Anywhere: from n/a through <= 2.0.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA CSRF vulnerability in the Prayer Times Anywhere WordPress plugin (versions <= 2.0.1) allows attackers to trick authenticated administrators into unknowingly submitting malicious requests that result in stored XSS payloads being saved to the database. When other users access affected pages, the embedded JavaScript executes in their browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Prayer Times Anywhere plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'Prayer Times Anywhere'. Note the installed version displayed.Affected if Plugin is installed and version is 2.0.1 or lower
-
Confirm plugin version is vulnerableCompare the installed version number to the affected range. The plugin is vulnerable in versions 2.0.1 and below.Affected if Installed version is 2.0.1 or any version below 2.0.1
-
Check if plugin is activeIn Plugins list, verify the Prayer Times Anywhere plugin shows as 'Active'. Only active instances can be exploited.Affected if Plugin is active with a vulnerable version
-
Inspect plugin settings for stored XSS payloadsAccess the plugin settings page (Prayer Times > Settings or similar). Inspect all text fields for suspicious JavaScript tags, script elements, or encoded payloads. Alternatively, query the wp_options table for option_name values related to the plugin and examine stored values.Affected if Plugin settings contain unrecognized or malicious script tags, event handlers (onload, onerror, onclick), or suspicious encoded content
-
Review recent admin activity logs for CSRF triggersCheck WordPress audit logs or server access logs for POST requests to admin-ajax.php or plugin admin pages originating from admin users that may indicate exploitation attempts.Affected if Unrecognized state-changing requests were made from admin sessions without proper CSRF tokens
A user is affected if the Prayer Times Anywhere plugin is installed, active, and running version 2.0.1 or lower, or if malicious XSS payloads are found stored in plugin settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to the latest version of Prayer Times Anywhere which includes CSRF token validation and proper input sanitization. If no update is available, implement anti-CSRF tokens on state-changing actions and enforce strict input validation on all user-supplied data.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22590 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data