dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-15508

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-04
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 Magic Import Document Extractor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.4 via the get_frontend_settings() function. This makes it possible for unauthenticated attackers to extract the site's magicimport.ai license key from the page source on any page containing the plugin's shortcode.

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

The Magic Import Document Extractor WordPress plugin versions up to 1.0.4 exposes the magicimport.ai license key through the get_frontend_settings() function in the HTML page source on any frontend page containing the plugin's shortcode. Unauthenticated attackers can view this information by inspecting the source code of affected pages.

MitigationUpdate the plugin to a version beyond 1.0.4 if available, or modify the get_frontend_settings() function to exclude the license key from being rendered in frontend page output.

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. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Magic Import Document Extractor' or check the plugin files in /wp-content/plugins/ directory for a folder containing 'magic-import' or similar
    Affected if Plugin is not installed on the WordPress site
  2. Check installed plugin version
    In WordPress admin > Plugins, find Magic Import Document Extractor and view the version number displayed below the plugin name, or read the main plugin PHP file header for 'Version:' field
    Affected if Version is 1.0.4 or lower (no fix version provided)
  3. Identify if shortcode is in use on frontend
    Search WordPress posts, pages, and widgets for the shortcode [magic_import] or similar by checking content in wp_posts database table or using a plugin to scan for shortcodes
    Affected if Shortcode is present and renders on any public-facing page
  4. Inspect page source for exposed license key
    Visit any frontend page that may contain the shortcode, right-click and 'View Page Source', then search for 'license_key', 'licence_key', or 'magicimport' or 'magic_import' in the HTML
    Affected if A license key value is visible in the HTML source code (the get_frontend_settings function is exposing it)
  5. Confirm exposure via get_frontend_settings
    In the browser dev tools (F12), inspect the page source or look for a JavaScript variable containing frontend settings; the license key should not be present in frontend output
    Affected if License key appears in frontend HTML output at all

A site is affected if the Magic Import Document Extractor plugin version 1.0.4 or lower is installed AND the shortcode is rendered on any frontend page, resulting in the license key being visible in the page source to unauthenticated visitors.

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 plugin to a version beyond 1.0.4 if available, or modify the get_frontend_settings() function to exclude the license key from being rendered in frontend page output.

Recommended fix High confidence

Version 1.0.5 or latest available release

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Magic Import Document Extractor' plugin
  4. Check if an update is available and update to the latest version (likely 1.0.5 or higher)
  5. Alternatively, download the latest version from the WordPress plugin repository and reinstall

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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