dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-1043

MEDIUM · 6.4 CVSS v3.1 Published 2025-02-20
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 Embed Any Document – Embed PDF, Word, PowerPoint and Excel Files plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.7.5 via the 'embeddoc' shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 Embed Any Document WordPress plugin fails to validate URLs passed through the 'embeddoc' shortcode, allowing authenticated attackers with Contributor-level or higher access to force the server to make arbitrary HTTP requests to internal or external locations. This SSRF can be used to enumerate internal services, access cloud metadata endpoints, or pivot to internal network resources.

MitigationUpdate the plugin to version 2.7.6 or later which contains proper URL validation. Until patched, restrict or disable the embeddoc shortcode for untrusted users and consider network-level filtering to block suspicious outbound requests.

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. Identify if Embed Any Document plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Embed Any Document' or check the plugin files in wp-content/plugins/embed-any-document/ for a version indicator
    Affected if Plugin is present and active in the WordPress installation
  2. Check installed plugin version
    In WordPress admin Plugins page, find Embed Any Document and note the version number displayed, or read the main plugin PHP file header for 'Version:' tag
    Affected if Version is lower than 2.7.6 (the patched version)
  3. Verify shortcode availability
    Check if the [embeddoc] shortcode is registered by searching plugin files for add_shortcode('embeddoc' or by attempting to use the shortcode in a post/page as a low-privilege user
    Affected if The [embeddoc] shortcode is registered and accessible
  4. Confirm low-privilege user access to shortcode
    Test creating or editing a post as a Contributor-level user and attempt to insert the [embeddoc] shortcode with a custom URL parameter
    Affected if Users with Contributor role or higher can use the shortcode without administrative oversight

Your environment is affected if the Embed Any Document plugin is installed with a version prior to 2.7.6 and the embeddoc shortcode is accessible to users with Contributor-level permissions or higher.

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 version 2.7.6 or later which contains proper URL validation. Until patched, restrict or disable the embeddoc shortcode for untrusted users and consider network-level filtering to block suspicious outbound requests.

Recommended fix Moderate confidence

Latest version beyond 2.7.5 (check wordpress.org for current release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Embed Any Document' plugin
  4. Check if current version is 2.7.5 or lower
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/embed-any-document and upload via Plugins > Add New > Upload Plugin
  7. Verify the update was successful and the plugin is functioning properly

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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