CVE-2014-125093
4.3 · MEDIUMOverview
CVE-2014-125093 is a medium-severity vulnerability affecting getadmiral ad_blocking_detector. It was published on March 10, 2023 and has a CVSS 3.1 base score of 4.3 (MEDIUM).
This vulnerability has a CVSS 3.1 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
Technical Description
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.
Remediation
Check the references section for vendor advisories and patches from getadmiral. Update ad_blocking_detector to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| getadmiral | ad_blocking_detector | >= 0, < 1.2.2 | Affected |
References
Frequently Asked Questions
What is CVE-2014-125093?
CVE-2014-125093 is a medium-severity vulnerability affecting getadmiral ad_blocking_detector. It was published on March 10, 2023 and has a CVSS 3.1 base score of 4.3 (MEDIUM).
How severe is CVE-2014-125093?
This vulnerability has a CVSS 3.1 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2014-125093?
Check the references section for vendor advisories and patches from getadmiral. Update ad_blocking_detector to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2014-125093?
CyberStrike's AI-powered security agents can automatically detect CVE-2014-125093 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related MEDIUM CVEs from 2014
View all →Multiple array index errors in drivers/media/video/msm/server/msm_cam_server.c in the MSM camera dri
The compat_sys_recvmmsg function in net/compat.c in the Linux kernel before 3.13.2, when CONFIG_X86_
Untrusted search path vulnerability in Bandisoft Bandizip before 3.10 allows local users to gain pri
Stack-based buffer overflow in udisks before 1.0.5 and 2.x before 2.1.3 allows local users to cause
Multiple array index errors in programs that are automatically generated by VBox/HostServices/Shared
The SetWiredProperty function in the D-Bus interface in WICD before 1.7.2 allows local users to writ
Untrusted search path vulnerability in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Wi
A race condition in the wmi_malware_scan.nbin plugin before 201402262215 for Nessus 5.2.1 allows loc
Integer overflow in the ping_init_sock function in net/ipv4/ping.c in the Linux kernel through 3.14.
Untrusted search path vulnerability in pam_motd (aka the MOTD module) in libpam-modules before 1.1.3
maintenservice_installer.exe in the Maintenance Service Installer in Mozilla Firefox before 29.0 and
The runtime WS component in the server in EMC RSA Access Manager 6.1.3 before 6.1.3.39, 6.1.4 before