CVE-2026-42673
Sensitive Data Exposure in Logtivity Activity Logs
Publication date: 2026-06-01
Last updated on: 2026-06-01
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| logtivity | logtivity | From 3.0.0 (inc) to 3.3.6 (inc) |
| logtivity | activity_logs | to 3.3.6 (inc) |
| logtivity | user_activity_tracking | to 3.3.6 (inc) |
| logtivity | multisite_activity_log | to 3.3.6 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-201 | The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-42673 is a vulnerability in the Logtivity WordPress plugin (versions 3.3.6 and earlier) that allows sensitive information to be inserted into sent data, which can then be retrieved by unauthorized parties.
This issue enables unauthenticated attackers to access sensitive information that should normally be restricted.
The vulnerability affects the Activity Logs, User Activity Tracking, and Multisite Activity Log components of the Logtivity plugin.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive information, which may be exploited by attackers to compromise the system further.
Because the vulnerability allows unauthenticated access, it increases the risk of data breaches without requiring the attacker to have prior access or credentials.
Users of the affected Logtivity plugin versions should update immediately to avoid potential exploitation.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability in Logtivity versions 3.3.6 and earlier allows unauthenticated attackers to access sensitive information. Immediate mitigation steps include:
- Update the Logtivity plugin to version 3.3.7 or later, where the issue has been patched.
- Apply the mitigation rule provided by Patchstack to block attacks until the update can be applied.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in Logtivity versions 3.3.6 and earlier allows unauthenticated attackers to access sensitive information that should be restricted. Exposure of sensitive data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require strict controls over personal and sensitive information to protect user privacy and ensure data security.
Because this vulnerability enables retrieval of embedded sensitive data, affected organizations may face increased risk of data breaches, potentially resulting in regulatory penalties or legal consequences if the exposed data includes personal or protected health information.
It is therefore critical for users of the affected Logtivity plugin versions to update to version 3.3.7 or apply mitigation measures to maintain compliance with these standards.