dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8845

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Islamic Database plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'islamicDB-roqya' shortcode in versions up to, and including, 1.0. This is due to insufficient input sanitization and output escaping on user-supplied 'width' and 'height' shortcode attributes within the islamicDB_sc_quran_qari_roqya() function, which are concatenated directly into HTML iframe attribute values. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The Islamic Database WordPress plugin has a stored XSS vulnerability in the islamicDB_sc_quran_qari_roqya() function where the 'width' and 'height' shortcode attributes are directly concatenated into HTML iframe attribute values without sanitization or escaping, allowing authenticated attackers with contributor+ access to inject malicious scripts.

MitigationImplement strict numeric validation and sanitization for width/height attributes, then apply proper HTML attribute escaping (such as esc_attr()) when outputting these values into iframe tags.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Islamic Database plugin is installed
    Check wp-content/plugins/ for a folder named 'islamic-database', 'islamic_db', or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'Islamic Database' or 'Quran Qari Roqya' related plugins.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named index.php, main.php, or islamic-db.php in the plugin folder) and look for the 'Version' header in the plugin comment block at the top. Alternatively, check the plugin row in WordPress Plugins admin page.
    Affected if Version is unknown or within any range that includes unpatched code (the vulnerability exists in unpatched versions)
  3. Locate the vulnerable shortcode function
    Search the plugin files for the function 'islamicDB_sc_quran_qari_roqya' or look for shortcode registration containing 'quran_qari_roqya' or similar. The function is typically in the main plugin file or a file handling shortcodes.
    Affected if The function exists in the plugin code and processes shortcode attributes
  4. Inspect the width/height attribute handling
    Examine the islamicDB_sc_quran_qari_roqya function code. Look for how 'width' and 'height' attributes are handled when building the iframe HTML tag. Check if esc_attr(), esc_html(), or any sanitization function wraps these values.
    Affected if The width/height attributes are directly concatenated into the iframe tag without esc_attr() or similar escaping (e.g., looks like '<iframe ... width="' . $width . '" height="' . $height . '" ...>')
  5. Determine if the shortcode is in use
    Check WordPress pages, posts, or widgets for the presence of the shortcode (typically [quran_qari_roqya] or similar) in content. Use WordPress search or database query on wp_posts for the shortcode string.
    Affected if The shortcode is actively used on any published content

A user is affected if the Islamic Database plugin is installed, contains the vulnerable function handling width/height attributes without escaping, and the shortcode is in use on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict numeric validation and sanitization for width/height attributes, then apply proper HTML attribute escaping (such as esc_attr()) when outputting these values into iframe tags.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8845 — 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-2026-8845 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