ad-ldap-connector's admin panel before version 5.0.13 does not provide csrf protection, which when exploited may result in remote code execution or confidential data loss. CSRF exploits may occur if the user visits a malicious page containing CSRF payload on the same machine that has access to the ad-ldap-connector admin console via a browser. You may be affected if you use the admin console included with ad-ldap-connector versions <=5.0.12. If you do not have ad-ldap-connector admin console enabled or do not visit any other public URL while on the machine it is installed on, you are not affected. The issue is fixed in version 5.0.13.
Severity
CVSS 3.1
8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
1.0%(unchanged from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 63rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-352Cross-Site Request Forgery (Cross Site Reference Forgery)
Show the promptExplain CVE-2020-15259 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-15259?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-15259?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-15259 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
auth0:ad\/ldap_connector
Versions
From the NVD's CPE matches.
Product
Affected
auth0:ad/ldap_connector
before 5.0.13
Attack patterns (CAPEC)
CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
CAPEC-462 Cross-Domain Search Timing Severity: Medium