Activity Log Plugin < 2.0.4 - Fulle Path Disclosure

2014-02-27 00:00

Strategic Overview

Status: Patched in 2.0.4
Affected Plugin: Activity Log – Monitor User and Agent Changes
Affected Version: < 2.0.4
CVSS: 7.5High
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE pending

View all Activity Log – Monitor User and Agent Changes vulnerabilities

At a glance

This record tracks a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Activity Log WordPress plugin, affecting versions < 2.0.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.0.4; sites on affected versions should update now. Disclosed February 2014.

Vulnerability Overview

The Activity Log plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 2.0.3 via direct calls to the ~/class-aal-integration-woocommerce.php file. This can allow unauthenticated attackers to extract sensitive data including the full path of the WordPress installation.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Activity Log < 2.0.4 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Activity Log the fix is 2.0.4: builds < 2.0.4 are affected, anything from 2.0.4 onward is not.

Remediation

Update to version 2.0.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Activity Log 2.0.4 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/97677968-9231-4a6b-ad81-ddb9eb9791dd

Related records

Other vulnerabilities in Activity Log – Monitor User and Agent Changes

CVSS Vector

7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/