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

CVE-2026-0688

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-02
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 Webmention plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 5.6.2 via the 'Tools::read' function. This makes it possible for authenticated attackers, with Subscriber-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 · moderate confidence

The Webmention WordPress plugin contains a Server-Side Request Forgery (SSRF) vulnerability in the Tools::read function in all versions up to 5.6.2. Authenticated attackers with Subscriber-level permissions can abuse this to make arbitrary HTTP requests from the server to internal or external resources, potentially enabling reconnaissance and access to internal services.

MitigationUpdate the Webmention plugin to the latest version beyond 5.6.2 which contains the patched code, or if no patch is available, remove the plugin until a fix is released.

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. Confirm Webmention plugin installation
    Check for the presence of the Webmention plugin in your WordPress installation: look for the directory wp-content/plugins/webmention/ or check the Plugins page in WordPress admin for 'Webmention' in the list of installed plugins.
    Affected if The Webmention plugin is installed on the WordPress site.
  2. Determine installed plugin version
    Open the main plugin file (usually wp-content/plugins/webmention/webmention.php) and look for the version declaration in the plugin header comment, or check the version column in the WordPress Plugins admin page.
    Affected if The installed version is 5.6.2 or lower.
  3. Verify subscriber-level access exists
    Check if there are user accounts with the Subscriber role on the site: go to Users > All Users in WordPress admin and review the roles assigned, or query the wp_users and wp_usermeta tables directly for users with wp_capabilities containing 'subscriber'.
    Affected if The site has at least one user account with Subscriber-level permissions, making exploitation possible.
  4. Confirm vulnerable function exists
    Inspect the plugin source code for the Tools::read function: open wp-content/plugins/webmention/lib/Tools.php (or similar path) and search for a function named 'read' within a 'Tools' class that performs HTTP requests.
    Affected if The Tools::read function exists and handles external HTTP requests without proper validation.

A user is affected if the Webmention plugin is installed with version 5.6.2 or lower and the site has subscriber-level user accounts that could trigger the vulnerable Tools::read function.

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 Webmention plugin to the latest version beyond 5.6.2 which contains the patched code, or if no patch is available, remove the plugin until a fix is released.

Recommended fix Moderate confidence

5.6.3 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Webmention plugin
  4. Check if an update is available and update to the latest version (5.6.3 or higher)
  5. Alternatively, download the latest version from wordpress.org/plugins/webmention/ and upload via Plugins > Add New > Upload Plugin
  6. Activate the updated plugin

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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