CVE-2026-12100
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 · uneditedThe URL Preview plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.0 via the 'url' parameter. This makes it possible for unauthenticated attackers 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 confidenceThe URL Preview WordPress plugin (versions up to 1.0) contains an SSRF vulnerability in the 'url' parameter. Unauthenticated attackers can supply arbitrary URLs that the vulnerable server will request, potentially reaching internal services, cloud metadata endpoints, or internal network resources.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm URL Preview plugin is installedCheck the WordPress plugins directory for a folder named 'url-preview' or similar. Look in /wp-content/plugins/ for any plugin with 'url preview' or 'url-preview' in the name.Affected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed plugin versionOpen the plugin's main PHP file or readme.txt in the plugin directory and look for the Version header comment or the version field in the plugin metadata.Affected if The version is 1.0 or lower, or no version is displayed (indicating an unpatched copy)
-
Locate the vulnerable endpointSearch plugin PHP files for handlers that process the 'url' parameter, typically in admin-ajax.php hooks or direct AJAX callback functions. Look for functions using $_GET['url'] or $_POST['url'].Affected if The plugin code contains a handler that accepts a 'url' parameter without proper validation
-
Verify the endpoint is accessibleCheck if the WordPress site responds to requests targeting the identified endpoint with a 'url' parameter. Examine access logs for requests to admin-ajax.php or similar endpoints containing 'url='.Affected if The endpoint processes 'url' parameters and returns any response indicating the request was made
-
Check for signs of exploitation attemptsReview server access logs and WordPress audit logs for unusual outbound requests, especially to internal IPs (10.x.x.x, 172.16-31.x.x, 192.168.x.x), localhost (127.0.0.1), or cloud metadata services (169.254.169.254).Affected if Logs show requests to internal or cloud metadata IP addresses that were not initiated by legitimate admin actions
You are affected if the URL Preview plugin is installed with version 1.0 or lower AND the plugin exposes a 'url' parameter handler that processes arbitrary URLs.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to a patched version if available. Otherwise, disable or remove the plugin until remediation is possible. If continued use is required, implement server-side allowlist validation for the 'url' parameter to restrict requests to trusted domains only.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12100 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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