dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-11997

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-11
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 Document Pro Elementor – Documentation & Knowledge Base plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.0.9. This is due to the plugin exposing sensitive Algolia API keys through the frontend JavaScript code via wp_localize_script without proper access restrictions. This makes it possible for unauthenticated attackers to view sensitive API keys in the page source, which could be leveraged to make unauthorized API calls to the configured Algolia search service.

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 Document Pro Elementor WordPress plugin exposes Algolia API keys in frontend JavaScript via wp_localize_script without access restrictions, allowing unauthenticated attackers to view sensitive credentials in page source and make unauthorized API calls.

MitigationReplace client-side exposed API keys with server-side authentication or a proxy, implement proper access controls, and rotate any exposed Algolia credentials immediately.

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. Identify if Document Pro Elementor plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or check the wp-content/plugins directory for a folder named 'document-pro-elementor' or similar
    Affected if The plugin is not installed on the WordPress site
  2. Check the installed plugin version
    In WordPress admin, view the plugin details to see the version number; compare against any known affected version ranges
    Affected if The installed version falls within an affected version range and the plugin is active
  3. View page source for exposed Algolia credentials
    Visit the frontend of the site, right-click and view page source, then search for 'algolia', 'application_id', 'api_key', or 'search_key' in the HTML
    Affected if Algolia Application ID, Search API Key, or Admin API Key appear in the page source in JavaScript variables
  4. Inspect wp_localize_script output
    In page source, look for a script tag containing localized data (typically with an object name like 'documentProSettings' or similar) that includes Algolia credentials
    Affected if A wp_localize_script call exposes Algolia keys to frontend JavaScript without access restrictions
  5. Verify Algolia integration is configured
    Check the plugin settings in WordPress admin for Algolia API configuration, or examine the exposed JavaScript for Algolia-specific configuration objects
    Affected if Algolia integration is enabled and credentials are being passed to client-side scripts

A user is affected if the Document Pro Elementor plugin is installed with Algolia integration active and Algolia API keys are visible in frontend page source via wp_localize_script.

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

Replace client-side exposed API keys with server-side authentication or a proxy, implement proper access controls, and rotate any exposed Algolia credentials immediately.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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