dbcve.org
VulnerabilityAwaiting classification

CVE-2026-12516

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 media-proxying endpoint, allowing anonymous users to make the site fetch arbitrary URLs, including internal and private-network addresses, and read back the response body. This results in a full-read Server-Side Request Forgery and open proxy.

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 versions before 1.5.8 contain an unauthenticated media-proxying endpoint that fails to validate destination URLs, enabling anonymous users to trigger the server to fetch arbitrary URLs (including internal/private network resources) and retrieve the response body - a full-read SSRF turning the site into an open proxy.

MitigationUpgrade to version 1.5.8 or later, which should implement proper URL validation and allowlisting for the proxy endpoint. Until patched, consider disabling or restricting access to the media-proxying functionality via web server rules.

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 Fediverse Embeds plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for the fediverse-embeds folder, or view the plugin in WordPress admin under Plugins > Installed Plugins
    Affected if The Fediverse Embeds plugin is not installed on the WordPress site
  2. Determine installed plugin version
    Open the main plugin file (usually fediverse-embeds.php) and locate the Version header in the plugin comment block, or check the plugin details in WordPress admin Plugins page
    Affected if The installed version is lower than 1.5.8 (e.g., 1.5.7, 1.5.6, etc.)
  3. Locate the media-proxying endpoint
    Search WordPress plugin files for patterns like 'media-proxy', 'proxy', or endpoint registration functions (add_action/add_filter with 'rest_api_init') that handle external URL fetching
    Affected if A media-proxying endpoint exists and is registered in the plugin (indicates the vulnerable feature is present)
  4. Verify endpoint accessibility
    Attempt to access common proxy endpoint paths such as /wp-json/fediverse-embeds/v1/proxy, /?rest_route=/fediverse-embeds/v1/proxy, or similar paths found in step 3, without providing authentication credentials
    Affected if The endpoint returns a response without requiring authentication (unauthenticated access is possible)

Your environment is affected if Fediverse Embeds plugin versions below 1.5.8 are installed and the unauthenticated media-proxying endpoint is accessible, allowing your server to be used as an open proxy for arbitrary 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

Upgrade to version 1.5.8 or later, which should implement proper URL validation and allowlisting for the proxy endpoint. Until patched, consider disabling or restricting access to the media-proxying functionality via web server rules.

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 in the list
  4. Check if an update is available; if so, click Update Now
  5. Alternatively, update via Plugins > Add New > Upload Plugin by uploading version 1.5.8 or later from the WordPress Plugin Repository
  6. After updating, verify the plugin version shows 1.5.8 or higher under Plugins > Installed Plugins

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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