CVE-2023-0812

Active Directory Integration / LDAP Integration <= 4.1.0 - Unauthenticated Information Disclosure

2023-04-19 00:00
István Márton

Strategic Overview

Status
Patched in 4.1.1
Affected Version
<= 4.1.0
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-0812
View all Active Directory Integration / LDAP Integration vulnerabilities

At a glance

CVE-2023-0812 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Active Directory Integration / LDAP Integration WordPress plugin, affecting versions <= 4.1.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.1.1; sites on affected versions should update now. Disclosed April 2023, reported by István Márton.

Vulnerability Overview

The Active Directory Integration / LDAP Integration plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 4.1.0 via the 'test_attribute_configuration'. This can allow unauthenticated attackers to extract sensitive data including configuration settings.

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.

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

Active Directory Integration / LDAP Integration <= 4.1.0 carries this weakness at test_attribute_configuration, and reaching it takes no account at all. 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 Active Directory Integration / LDAP Integration the fix is 4.1.1: builds <= 4.1.0 are affected, anything from 4.1.1 onward is not.

Remediation

Update to version 4.1.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Active Directory Integration / LDAP Integration 4.1.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C