WordPress security by component
Document Library Lite
Plugin description
Document Library Lite is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Dec 16, 2025; the highest published CVSS base score is 5.9.
Plugin slug:
document-library-liteLatest vulnerability
CVE-2025-67986: Document Library Lite: Cross-site scripting
Document Library Lite is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Dec 16, 2025 |
CVE-2025-67986
Document Library Lite: Cross-site scripting
Document Library Lite is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.9
NVDPending
|
| Dec 16, 2025 |
CVE-2025-67985
Document Library Lite: A security weakness
Document Library Lite is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Nov 01, 2025 |
CVE-2025-11174
Document Library Lite: A security weakness
Document Library Lite is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.3
NVDPending
|