dbcve.org
Daily Prayer TimeWordPress extension · Mmrs151

CVE-2023-27631

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-22
Fix available
A fix is available. Upgrade to after 2023.05.04 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in mmrs151 Daily Prayer Time plugin <= 2023.05.04 versions.

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 confidence

Authenticated contributor+ users can inject malicious scripts via stored XSS in the mmrs151 Daily Prayer Time plugin versions 2023.05.04 and below. The malicious payload persists and executes when other users view the affected content.

MitigationUpdate the Daily Prayer Time plugin to a version newer than 2023.05.04. If no update is available, remove the plugin or implement input sanitization/output encoding in the plugin code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Daily Prayer TimeWordPress extension
Affected:<= 2023.05.04

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Mmrs151 Daily Prayer Time plugin is installed
    Check the WordPress wp-content/plugins directory for a folder named 'mmrs151-daily-prayer-time' or similar variant. In the WordPress admin, go to Plugins > Installed Plugins and look for 'Daily Prayer Time' or 'Mmrs151 Daily Prayer Time' in the list.
    Affected if The plugin appears in the installed plugins list or filesystem
  2. Determine the installed plugin version
    If the plugin is installed, open the main plugin PHP file (usually named similarly to the folder, e.g., daily-prayer-time.php) and locate the version comment in the plugin header: 'Version: x.x.xx' or check the readme.txt file for the 'Stable tag' entry.
    Affected if The version number is 2023.05.04 or lower
  3. Verify if contributor or higher role users exist
    In WordPress admin, go to Users > All Users and check if any users have the role of Contributor, Author, Editor, or Administrator. Alternatively, query the wp_usermeta table for wp_capabilities containing 'contributor' or higher roles.
    Affected if At least one user with Contributor-level access or higher exists in the system
  4. Confirm plugin functionality is active
    Check if the Daily Prayer Time shortcode or widget is being used on the site. Look for '[daily_prayer_time]' or similar shortcode in posts/pages, or check the plugin settings page at Plugins > Installed Plugins > Daily Prayer Time > Settings to see if times have been configured and saved.
    Affected if The plugin settings have been configured and saved, or the shortcode/widget is in use on any page
  5. Inspect stored plugin data for malicious scripts
    Query the WordPress database, specifically the wp_options table for option_name values like 'mmrs151_dpt_settings' or similar, and examine the stored values. Also check any custom post meta tables where the plugin may store prayer time configurations. Look for patterns like '<script', 'javascript:', 'onerror=', 'onload=' within the stored data.
    Affected if Any stored data contains unsanitized HTML or JavaScript payload fragments

The user is affected if the Mmrs151 Daily Prayer Time plugin version 2023.05.04 or lower is installed, the plugin is actively configured, and users with Contributor-level access or higher exist in the WordPress environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2023.05.04
Interim mitigation

Update the Daily Prayer Time plugin to a version newer than 2023.05.04. If no update is available, remove the plugin or implement input sanitization/output encoding in the plugin code.

Fix this in Daily Prayer Time Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27631 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-27631 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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