dbcve.org
Daily Prayer TimeWordPress extension · Mmrs151

CVE-2023-47817

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to after 2023.10.13 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in mmrs151 Daily Prayer Time plugin <= 2023.10.13 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

Stored Cross-site Scripting (XSS) vulnerability in the mmrs151 Daily Prayer Time WordPress plugin (versions <= 2023.10.13). The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing authenticated attackers to inject malicious JavaScript that executes in victim browsers.

MitigationUpdate the mmrs151 Daily Prayer Time plugin to the latest version beyond 2023.10.13 which contains the security patch. If no update is available, remove or replace the plugin.

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.10.13

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. Verify the mmrs151 Daily Prayer Time plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'mmrs151 Daily Prayer Time' in the list of active and inactive plugins.
    Affected if The plugin appears in the installed plugins list regardless of activation status.
  2. Determine the installed plugin version
    In the plugins list, locate the mmrs151 Daily Prayer Time entry. Click on the plugin name or view the plugin details to find the version number displayed (typically displayed below the plugin name).
    Affected if The displayed version number is 2023.10.13 or earlier.
  3. Check plugin activity status
    In the WordPress plugins admin page, verify whether mmrs151 Daily Prayer Time shows as 'Active' or 'Inactive' under the plugin status column.
    Affected if The plugin is currently activated, as the XSS executes when the vulnerable output is rendered on pages viewed by users.
  4. Inspect plugin settings for user-supplied input
    Access the plugin settings page (usually under Settings or a dedicated menu item named 'Daily Prayer Time' or similar). Identify any input fields where users can submit or configure data such as location names, mosque names, or custom text.
    Affected if The plugin contains input fields that accept user-supplied text and save this data for later display on the website.
  5. Review stored data in plugin database tables
    Access the WordPress database via phpMyAdmin or command line. Look for tables prefixed with wp_ that may contain mmrs151 or prayer_time related data. Query for any stored values that might contain injected script tags.
    Affected if The database contains entries with unescaped HTML or script tags in fields related to the plugin's configurable parameters.

You are affected if the mmrs151 Daily Prayer Time plugin is installed at version 2023.10.13 or earlier and is active, as the stored XSS vulnerability exists in how the plugin renders unsanitized user input on webpages.

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.10.13
Interim mitigation

Update the mmrs151 Daily Prayer Time plugin to the latest version beyond 2023.10.13 which contains the security patch. If no update is available, remove or replace the plugin.

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-47817 — 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-47817 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