CVE-2026-3569
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 Liaison Site Prober plugin for WordPress is vulnerable to Information Exposure in all versions up to and including 1.2.1 via the /wp-json/site-prober/v1/logs REST API endpoint. The permissions_read() permission callback unconditionally returns true (via __return_true()) instead of checking for appropriate capabilities. This makes it possible for unauthenticated attackers to retrieve sensitive audit log data including IP addresses, user IDs, usernames, login/logout events, failed login attempts, and detailed activity descriptions.
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 Liaison Site Prober WordPress plugin has an insecure REST API endpoint (/wp-json/site-prober/v1/logs) that uses __return_true() as its permission callback, allowing unauthenticated users to access sensitive audit log data including IP addresses, user IDs, usernames, and login/logout events.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Liaison Site Prober plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'site-prober' or 'liaison-site-prober'. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to confirm the plugin is listed.Affected if The plugin is present in the WordPress installation
-
Check the installed plugin versionIn the WordPress admin, find the plugin in the Plugins list and note the version number displayed beneath the plugin name. Compare this version against any official release notes from the plugin developer that mention security fixes for CVE-2026-3569.Affected if The installed version predates the patched version that implements proper capability checking
-
Test the vulnerable REST API endpointSend a GET request to the endpoint /wp-json/site-prober/v1/logs using a tool like curl or a browser, for example: curl https://yourdomain.com/wp-json/site-prober/v1/logs. Do not include any authentication headers.Affected if The endpoint returns an HTTP 200 response without requiring authentication (status 401 or 403 would indicate the vulnerability may be patched)
-
Inspect the endpoint response for sensitive dataExamine the JSON response from the /wp-json/site-prober/v1/logs endpoint. Look for the presence of IP addresses, user IDs, usernames, login events, or logout events within the returned data structure.Affected if The response contains audit log data including IP addresses, user identifiers, usernames, or login/logout event records
A user is affected if the Liaison Site Prober plugin is installed and the /wp-json/site-prober/v1/logs endpoint is accessible without authentication and returns sensitive audit log information.
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 that implements proper capability checking in the permissions_read() callback, or disable the plugin until a fix is available.
- 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-3569 — 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-3569 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