dbcve.org
VulnerabilityAwaiting classification

CVE-2026-12517

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-09
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 7 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 Fediverse Embeds WordPress plugin before 1.5.8 does not validate the destination of the server-side request performed by an unauthenticated site-info endpoint before fetching it, allowing anonymous users (the gating nonce is exposed on public pages carrying an embed) to make the site request internal and private-network URLs and read back the parsed page metadata. This is a Server-Side Request Forgery.

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 Fediverse Embeds WordPress plugin before 1.5.8 contains an unauthenticated site-info endpoint that accepts a URL parameter without validating whether the target is an internal/private network resource. Because the nonce protecting this endpoint is exposed on public embed pages, anonymous attackers can supply internal URLs (e.g., http://localhost, http://192.168.1.x) and retrieve parsed metadata, enabling reconnaissance of internal services.

MitigationUpdate the Fediverse Embeds plugin to version 1.5.8 or later, which includes proper destination validation. If immediate updating is not possible, restrict access to the vulnerable endpoint at the web server level or disable the plugin until patched.

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. Confirm plugin installation and version
    Check the plugin header in wp-content/plugins/fediverse-embeds/fediverse-embeds.php for the Version field, or query the WordPress plugins API endpoint /wp-json/wp/v2/plugins?search=fediverse-embeds
    Affected if The installed version is below 1.5.8 (e.g., 1.5.7, 1.5.6, etc.)
  2. Verify the vulnerable endpoint is reachable
    Send a GET request to /?fediverse_embed_site_info=1&url=http://127.0.0.1 (or the plugin's actual endpoint URL as defined in the plugin code) without authentication
    Affected if The endpoint returns a response without requiring authentication or rejecting internal network targets
  3. Check if embed pages expose the nonce
    Visit a public embed page (e.g., any post with a Fediverse embed) and view the page source; search for a nonce value in a hidden field or JavaScript variable related to the fediverse_embed action
    Affected if A nonce value tied to the site-info functionality is visible in the publicly accessible embed page HTML
  4. Test for SSRF on the endpoint
    Send a crafted request to the site-info endpoint with an internal URL (e.g., url=http://localhost or url=http://192.168.1.1) and observe whether the server returns metadata from that internal resource
    Affected if The endpoint successfully retrieves and returns content from internal/private network addresses, confirming the SSRF vulnerability exists

The environment is affected if the Fediverse Embeds plugin version is below 1.5.8 AND the site-info endpoint is accessible without authentication and accepts internal network URLs.

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 Fediverse Embeds plugin to version 1.5.8 or later, which includes proper destination validation. If immediate updating is not possible, restrict access to the vulnerable endpoint at the web server level or disable the plugin until patched.

Recommended fix High confidence

Fediverse Embeds version 1.5.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Fediverse Embeds plugin
  4. Check the current version number
  5. If the installed version is below 1.5.8, click Update Now to upgrade to version 1.5.8
  6. Alternatively, download version 1.5.8 or later from the WordPress plugin repository and upload/install it manually
  7. After upgrading, verify the fix by checking that the site-info endpoint properly validates URLs before making server-side requests

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.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-2026-12517 — 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-12517 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