Security readout for executives and security teams
Plain-English summary
CVE-2006-6575 affects Yet Another PHP LDAP Admin Project, also called yaplap, versions 0.6 and 0.6.1. A flaw in ldap.php can let a remote attacker cause the server to load attacker-controlled PHP through the LOGIN_style parameter, potentially leading to arbitrary code execution.
Executive priority
Treat confirmed internet-facing deployments as urgent. The application is old, the issue may allow server-side code execution, and no patch details are available in the provided sources.
Technical view
The source bundle describes a PHP remote file inclusion issue in ldap.php. The vulnerable input is LOGIN_style, which may accept a URL and include remote PHP code. Affected versions are listed as yaplap 0.6 and 0.6.1. No CVSS, CWE, vendor patch, or official mitigation is provided.
Likely exposure
Exposure is likely limited to organizations still running the old yaplap 0.6 or 0.6.1 PHP LDAP administration application, especially if ldap.php is reachable from untrusted networks.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, so active exploitation is not established. A public Exploit-DB reference exists, which indicates public exploit information is available, but the bundle does not prove current attacks.
Researcher notes
Evidence is sparse but consistent: the CVE description identifies remote file inclusion through LOGIN_style in ldap.php, affecting yaplap 0.6 and 0.6.1. Avoid assuming broader product impact, modern exploit activity, or a specific vendor fix from this bundle alone.
Mitigation direction
- Identify and retire any yaplap 0.6 or 0.6.1 deployments.
- Check vendor or project guidance for any available fixed release.
- Restrict access to yaplap administration paths to trusted networks only.
- Remove public exposure if the application is no longer required.
- Review PHP configuration and hosting controls for remote include risk.
Validation and detection
- Inventory web servers for yaplap files, especially ldap.php.
- Confirm any discovered yaplap version before determining exposure.
- Review logs for suspicious ldap.php requests involving LOGIN_style.
- Check whether the application is reachable from the internet.
- Document compensating controls if replacement cannot happen immediately.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2006-6575 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- 2930CVE reference · exploit, x_refsource_EXPLOIT-DB
- yaplap-ldap-file-include(30887)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.