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

CVE-2026-15284

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-10
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 6 weeks old

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 King Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'form_page_id' parameter in versions up to, and including, 51.1.62 This is due to insufficient input sanitization in the add_to_submissions() function, which applies sanitize_text_field() (which preserves double-quote characters) before storing the value in post meta, combined with missing output escaping in the king_addons_submissions_custom_column_content() function, which concatenates the stored value into an HTML href attribute via admin_url() without wrapping the result in esc_url(). This makes it possible for authenticated attackers, with subscriber-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

Stored XSS vulnerability in King Addons for Elementor plugin allows authenticated attackers with subscriber-level access to inject arbitrary JavaScript via the 'form_page_id' parameter. The function add_to_submissions() uses sanitize_text_field() which preserves double-quote characters, and king_addons_submissions_custom_column_content() outputs the value in an href attribute without escaping, causing the stored malicious script to execute when users access the affected admin pages.

MitigationUpdate King Addons for Elementor to version 51.1.63 or later, which should implement proper output escaping using esc_url() or esc_attr() for the form_page_id value when rendering in HTML attributes.

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 King Addons for Elementor is installed
    Navigate to WordPress admin > Plugins and locate 'King Addons for Elementor' in the installed plugins list, or check the /wp-content/plugins/king-addons-for-elementor/ directory exists
    Affected if The plugin is present in the environment
  2. Identify installed plugin version
    In WordPress admin > Plugins, click on the plugin to view version details, or read the 'readme.txt' or 'index.php' file in the plugin directory for the 'Version' header
    Affected if The version is lower than 51.1.63 (the patched version)
  3. Confirm submissions feature is active
    Check if the King Addons submissions functionality is enabled: look for 'Submissions' menu item in the King Addons admin menu, or check if 'enable_submissions' option exists in wp_options table
    Affected if The submissions feature is enabled and accessible to subscriber-level users
  4. Inspect submissions database for suspicious form_page_id values
    Query the WordPress database: SELECT * FROM wp_kingaddons_submissions WHERE form_page_id LIKE '%javascript:%' OR form_page_id LIKE '%onload=%' OR form_page_id LIKE '"%'
    Affected if Any records contain double-quote characters, 'javascript:' protocol handlers, or event handlers in the form_page_id field
  5. Review admin access logs for form_page_id parameter exploitation
    Check web server access logs and WordPress audit logs for POST/GET requests to submission-related endpoints containing unusual form_page_id values with quotes or script tags
    Affected if Logs show requests with form_page_id values containing quotes, script tags, or event handlers from subscriber accounts

A user is affected if the King Addons for Elementor plugin is installed with a version lower than 51.1.63, the submissions feature is enabled, and either malicious form_page_id values exist in the database or exploitation attempts are visible in logs.

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

Update King Addons for Elementor to version 51.1.63 or later, which should implement proper output escaping using esc_url() or esc_attr() for the form_page_id value when rendering in HTML attributes.

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