Liaison Site Prober Plugin up to 1.2.1 on WordPress REST API Endpoint logs permissions_read authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Liaison Site Prober Plugin up to 1.2.1 on WordPress. It has been classified as problematic. This vulnerability affects the function permissions_read of the file /wp-json/site-prober/v1/logs of the component REST API Endpoint. This manipulation causes authorization.
The identification of this vulnerability is CVE-2026-3569. It is possible to initiate the attack remotely. There is no exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability has been found in Liaison Site Prober Plugin up to 1.2.1 on WordPress and classified as problematic. Affected by this vulnerability is the function permissions_read of the file /wp-json/site-prober/v1/logs of the component REST API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality. The summary by CVE is:
The 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.
The weakness was shared by Itthidej Aramsri. The advisory is shared at wordfence.com. This vulnerability is known as CVE-2026-3569 since 03/04/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
Upgrading to version 1.2.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25406). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (Wordfence): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Site Prober Plugin 1.2.1
Timeline
03/04/2026 CVE reserved04/24/2026 Advisory disclosed
04/24/2026 VulDB entry created
04/24/2026 VulDB entry last update
Sources
Advisory: wordfence.comResearcher: Itthidej Aramsri
Status: Confirmed
CVE: CVE-2026-3569 (🔒)
GCVE (CVE): GCVE-0-2026-3569
GCVE (VulDB): GCVE-100-359329
EUVD: 🔒
Entry
Created: 04/24/2026 10:46Updated: 04/24/2026 15:45
Changes: 04/24/2026 10:46 (68), 04/24/2026 15:45 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.