dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-13997

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 King Addons for Elementor – 4,000+ ready Elementor sections, 650+ templates, 70+ FREE widgets for Elementor plugin for WordPress is vulnerable to unauthenticated API key disclosure in all versions up to, and including, 51.1.49 due to the plugin adding the API keys to the HTML source code via render_full_form function. This makes it possible for unauthenticated attackers to extract site's Mailchimp, Facebook and Google API keys and secrets. This vulnerability requires the Premium license to be installed

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 King Addons for Elementor plugin versions up to 51.1.49 expose API keys for Mailchimp, Facebook, and Google services in the HTML source code via the render_full_form function. Unauthenticated attackers can extract these credentials directly from the page HTML.

MitigationUpdate the King Addons for Elementor plugin to version 51.1.50 or later. Additionally, rotate any API keys that may have been exposed as a precautionary measure.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Check if King Addons for Elementor is installed
    In WordPress admin, go to Plugins and look for 'King Addons for Elementor' or check the plugin files in wp-content/plugins/king-addons-for-elementor/ for a version file
    Affected if The plugin is present on the WordPress site
  2. Determine the installed plugin version
    View the plugin version in the WordPress plugin list or read the main plugin file header (e.g., king-addons-for-elementor.php) to find the Version: field
    Affected if Version is 51.1.49 or lower (any version up to and including 51.1.49)
  3. Identify pages using form widgets that call render_full_form
    Search WordPress pages/posts for Elementor form widgets from King Addons, or review Elementor template assignments. The vulnerable function render_full_form is triggered when form fields are displayed on the frontend.
    Affected if Any frontend page displays a form built with King Addons Elementor widgets
  4. Inspect HTML source for exposed API credentials
    View the source HTML of a page containing a King Addons form (right-click > View Page Source or use browser dev tools). Search for strings like 'mailchimp', 'facebook', 'google', 'api_key', or look for long alphanumeric strings in script tags or data attributes.
    Affected if API keys for Mailchimp, Facebook, or Google services appear in plain text within the page HTML

A site is affected if it runs King Addons for Elementor version 51.1.49 or lower and has any form widget rendered on the frontend, allowing unauthenticated visitors to view exposed API credentials in the HTML source.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the King Addons for Elementor plugin to version 51.1.50 or later. Additionally, rotate any API keys that may have been exposed as a precautionary measure.

Recommended fix High confidence

51.1.50 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'King Addons for Elementor' plugin
  4. Check if update is available and update to latest version (version 51.1.50 or higher)
  5. Alternatively, download the latest version from wordpress.org/plugins/king-addons-for-elementor/ and upload via Plugins > Add New > Upload Plugin

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed 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 help mitigating

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-2025-13997 — 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-2025-13997 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