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

CVE-2026-4074

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-22
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 Quran Live Multilanguage plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'cheikh' and 'lang' shortcode attributes in all versions up to, and including, 1.0.3. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. The quran_live_render() function of quran-live.php receives shortcode attributes and passes them directly through shortcode_atts() and extract() without any sanitization. These values are then passed to Render_Quran_Live::render_verse_quran_live() where they are echoed directly into inline <script> blocks using PHP short tags (<?=$cheikh;?> and <?=$lang;?>) at lines 191, 216, 217, 245, and 246 of Class_QuranLive.php. Since the output occurs inside a JavaScript context within <script> tags, an attacker can break out of the JavaScript string and inject arbitrary script code. 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 Quran Live Multilanguage WordPress plugin fails to sanitize shortcode attributes ('cheikh' and 'lang') before using them in inline JavaScript. The quran_live_render() function passes unsanitized input through extract() to Render_Quran_Live::render_verse_quran_live(), which echoes values directly into <script> blocks using PHP short tags without escaping. Attackers with Contributor-level access can inject arbitrary JavaScript by breaking out of string contexts.

MitigationUpgrade to the latest version of the plugin which properly sanitizes shortcode attributes and escapes output before embedding in JavaScript contexts, or implement proper input validation and output encoding (e.g., json_encode()) for all shortcode attributes before use in script 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 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Quran Live Multilanguage' or check wp-content/plugins directory for quran-live or similar naming
    Affected if Plugin is present in the WordPress installation
  2. Check installed version
    View plugin details in WordPress admin plugins list, or read version from plugin's main PHP file header in wp-content/plugins/
    Affected if Version is unknown, older than current, or the plugin file lacks version metadata (indicating outdated/unpatched)
  3. Locate vulnerable shortcode handler
    In the plugin directory, search for function quran_live_render() or the shortcode registration - typically in the main plugin file
    Affected if Function exists and uses extract() on shortcode attributes without sanitization
  4. Inspect attribute handling in render function
    Open the file containing render_verse_quran_live() method - look for direct echo/print of $cheikh or $lang variables inside <script> tags without escaping (check for missing esc_js(), json_encode(), or similar)
    Affected if Attributes are output directly into JavaScript context without encoding (e.g., no esc_attr(), esc_js(), or json_encode() wrapping)
  5. Search for shortcode usage in content
    Query WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%[quran_live%' OR check pages/posts for the shortcode visually
    Affected if The shortcode is present and contains unusual attribute values (e.g., quotes, script keywords, event handlers)
  6. Review shortcode attribute values in database
    Export posts containing the shortcode and inspect 'cheikh' and 'lang' attribute values for injected JavaScript patterns like onerror=, alert(, document.cookie, or broken string contexts
    Affected if Any shortcode instances contain unsanitized user-controlled values that could execute as JavaScript

A user is affected if the Quran Live Multilanguage plugin is installed, the vulnerable shortcode is in use, and the code outputs shortcode attributes directly into script tags without encoding - particularly if Contributor-level users can edit content.

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

Upgrade to the latest version of the plugin which properly sanitizes shortcode attributes and escapes output before embedding in JavaScript contexts, or implement proper input validation and output encoding (e.g., json_encode()) for all shortcode attributes before use in script tags.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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