Skip to main content

Logtivity WordPress Plugin EUVDEUVD-2026-28914

| CVE-2026-8198 MEDIUM
Information Exposure (CWE-200)
2026-05-09 Wordfence GHSA-5rh7-8226-g7fr
5.3
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

2
Analysis Generated
May 09, 2026 - 13:15 vuln.today
CVE Published
May 09, 2026 - 12:29 nvd
MEDIUM 5.3

DescriptionCVE.org

The Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity plugin for WordPress is vulnerable to Authentication Bypass to Information Disclosure in versions up to, and including, 3.3.6. This is due to a logic flaw in the verifyAuthorization method where requests without an Authorization header skip Bearer token validation and fall through to an unconditional return true statement, bypassing all authentication checks. This makes it possible for unauthenticated attackers to access the /wp-json/logtivity/v1/options REST API endpoint and retrieve all plugin configuration options, including the logtivity_site_api_key which can be used to impersonate the site in API calls to the Logtivity service.

AnalysisAI

Unauthenticated attackers can bypass REST API authentication in the Logtivity plugin (versions up to 3.3.6) via a logic flaw in the verifyAuthorization method, allowing direct access to the /wp-json/logtivity/v1/options endpoint and disclosure of sensitive configuration including the logtivity_site_api_key. This key can be leveraged to impersonate the affected WordPress site in API calls to the Logtivity service. CVSS 5.3 (low confidentiality impact) reflects information disclosure severity; no active exploitation in CISA KEV at time of analysis.

Technical ContextAI

The Logtivity plugin exposes REST API endpoints through WordPress's /wp-json/ infrastructure. The verifyAuthorization method in Logtivity_Rest_Endpoints.php implements Bearer token validation for API requests but contains a critical logic flaw: requests lacking an Authorization header entirely bypass token checking and unconditionally return true, falling through to an allow-all default case. This violates CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) by exposing REST endpoints that should require authentication. The affected endpoint /wp-json/logtivity/v1/options returns plugin configuration including the logtivity_site_api_key, a credential used for Logtivity service authentication. The vulnerability exists because the method fails to reject requests absent valid authorization before returning success.

RemediationAI

Upgrade immediately to version 3.3.7 or later, which restores proper authentication validation in the verifyAuthorization method. Update via WordPress admin dashboard (Plugins > Installed Plugins > Logtivity > Update) or manually download from plugins.wordpress.org. If immediate patching is delayed, disable the Logtivity plugin entirely via wp-plugin deactivate logtivity (command-line) or manually from wp-admin/plugins.php, removing REST endpoint exposure until patch deployment; note that this also disables activity logging functionality. As an interim compensating control, use a Web Application Firewall (WAF) to block all requests to /wp-json/logtivity/* endpoints for untrusted source IPs, or implement .htaccess-based IP whitelisting to the /wp-json/ directory if Logtivity API calls originate only from known administrative networks. If the logtivity_site_api_key has been exposed, immediately rotate the credential via the Logtivity service dashboard and audit past API activity for unauthorized access.

CVE-2016-10045 CRITICAL POC
9.8 Dec 30

The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-8353 CRITICAL POC
9.8 Sep 28

The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-3495 CRITICAL POC
9.8 May 22

The Country State City Dropdown CF7 plugin for WordPress is vulnerable to SQL Injection via the ‘cnt’ and 'sid' paramete

Share

EUVD-2026-28914 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy