LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125093: Ad Blocking Detector Plugin ad-blocking-detector.php information disclosure

A vulnerability has been found in Ad Blocking Detector Plugin up to 1.2.1 on WordPress and classified as problematic. This vulnerability affects unknown code of the file ad-blocking-detector.php. The manipulation leads to information disclosure. The attack can be initiated remotely. Upgrading to version 1.2.2 is able to address this issue. The patch is identified as 3312b9cd79e5710d1e282fc9216a4e5ab31b3d94. It is recommended to upgrade the affected component. VDB-222610 is the identifier assigned to this vulnerability.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity information disclosure issue in the WordPress Ad Blocking Detector Plugin versions 1.2.0 and 1.2.1. A remote attacker with some privileges could obtain limited information through ad-blocking-detector.php. Public sources name version 1.2.2 as the fix.

Executive priority

Prioritize routine remediation for WordPress properties using this plugin. The issue is not marked as actively exploited, but patching is straightforward and reduces avoidable information leakage from public-facing sites.

Technical view

CVE-2014-125093 is classified as CWE-200 information exposure. The affected file is ad-blocking-detector.php, but the public bundle does not describe the exact data disclosed. CVSS 3.1 is 4.3 with network attack vector, low complexity, required privileges, no user interaction, and low confidentiality impact only.

Likely exposure

Exposure is limited to WordPress sites running Ad Blocking Detector Plugin 1.2.0 or 1.2.1. Sites already upgraded to 1.2.2 are identified as fixed by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The CVSS vector indicates network reachability and low attack complexity, but privileges are required. Treat this as a plausible authenticated information disclosure risk, not confirmed in-the-wild exploitation.

Researcher notes

Public detail is sparse: the vulnerable code path and exposed data are not described in the bundle. The strongest facts are affected versions, CWE-200 classification, CVSS PR:L, and the 1.2.2 patch reference.

Mitigation direction

  • Upgrade Ad Blocking Detector Plugin to version 1.2.2 or later.
  • Confirm the patched commit is included in the deployed plugin code.
  • Restrict WordPress accounts to least privilege until upgraded.
  • Check vendor or plugin repository guidance for any additional remediation.

Validation and detection

  • Inventory WordPress sites for Ad Blocking Detector Plugin installations.
  • Verify installed plugin versions are not 1.2.0 or 1.2.1.
  • Review access logs for unusual requests involving ad-blocking-detector.php.
  • Confirm the site is not running the vulnerable plugin from cached or copied code.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-125093 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2014-125093Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAd Blocking Detector Plugin1.2.0, 1.2.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.