CVE-2026-8845 MEDIUM

CVE-2026-8845: Islamic Database <= 1.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes

Vendor Samiullah-Kaifi
Product Islamic Database
Weakness CWE-79 · XSS
Published May 27, 2026
Last update May 27, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Islamic Database versions 1.0 and earlier contain a cross-site scripting vulnerability that allows authenticated users to inject malicious scripts. The vulnerability has scope change, meaning injected code can affect other users or components beyond the vulnerable input field. An attacker with low-level account access can craft malicious input that executes in other users' browsers, potentially stealing session data or performing actions on their behalf.

What an attacker can do

03Attacker Capabilities

Inject JavaScript that runs in other users' browsers and steals their session data or performs actions as them.

Potential impact on your site

04Site Impact

Authenticated users can compromise other users' accounts or sessions; data confidentiality and integrity are at risk.

Conditions required to exploit

05Prerequisites

Attacker needs a low-privilege account on the site; no user interaction required from the victim.

Key dates

06Disclosure timeline

May 27, 2026 CVE published
May 27, 2026 Record updated