CVE-2023-2599

Active Directory Integration / LDAP Integration <= 4.1.4 - Cross-Site Request Forgery to SQL Injection

2023-05-12 00:00
Marco Wotschka

Strategic Overview

Status
Patched in 4.1.5
Affected Plugin
Active Directory Integration / LDAP Integration
Affected Version
<= 4.1.4
CVSS
3.1Low
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-2599
View all Active Directory Integration / LDAP Integration vulnerabilities

At a glance

CVE-2023-2599 is a low-severity Cross-Site Request Forgery (CSRF) vulnerability in the Active Directory Integration / LDAP Integration WordPress plugin, affecting versions <= 4.1.4. It carries a CVSS score of 3.1 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 4.1.5; sites on affected versions should update now. Disclosed May 2023, reported by Marco Wotschka.

Vulnerability Overview

The Active Directory Integration plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to time-based SQL Injection via the orderby and order parameters in versions up to, and including, 4.1.4 due to missing nonce verification on the get_users function and insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to cause resource exhaustion via a forged request granted they can trick an administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Active Directory Integration / LDAP Integration <= 4.1.4 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Active Directory Integration / LDAP Integration the fix is 4.1.5: builds <= 4.1.4 are affected, anything from 4.1.5 onward is not.

Remediation

Update to version 4.1.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Active Directory Integration / LDAP Integration: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Active Directory Integration / LDAP Integration 4.1.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-2599https://www.wordfence.com/threat-intel/vulnerabilities/id/74089b16-76fa-4654-9007-3f0c2e894894https://nvd.nist.gov/vuln/detail/CVE-2023-2599

Related records

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