# CVE-2022-0403: Library File Manager < 5.2.3 - Subscriber+ Arbitrary File Creation/Upload/Deletion

- Exploited (CISA KEV): no
- Published: 2022-04-04
- CVSS: not scored
- EPSS: 1.3% (69th percentile)
- CWE: CWE-434

The Library File Manager WordPress plugin before 5.2.3 is using an outdated version of the elFinder library, which is know to be affected by security issues (CVE-2021-32682), and does not have any authorisation as well as CSRF checks in its connector AJAX action, allowing any authenticated users, such as subscriber to call it. Furthermore, as the options passed to the elFinder library does not restrict any file type, users with a role as low as subscriber can Create/Upload/Delete Arbitrary files and folders.

## Edge WAF coverage (claimed by vendors, not measured)

| Vendor | Status | First rule | Days after publication |
|---|---|---|---|
| Cloudflare | Before feed history | — | — |
| AWS | No public claim | — | — |
| Microsoft Azure | No public claim | — | — |
| Google Cloud | Before feed history | — | — |
| Fastly | Before feed history | — | — |
| F5 | Rule published | 2026-09-16 | 1626 |
| Akamai | No public source | — | — |
| OWASP CRS | Before feed history | — | — |

### F5

- 2026-09-16 · new · rule 200013218
  > Added: signature 200013218 "WordPress Library File Manager Broken Access Control" (Authentication/Authorization Attacks, risk Medium), systems: WordPress. References: CVE-2022-0403.
  Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog

"No public claim" means no vendor statement names this CVE; "Before feed history" means the CVE is older than the vendor feed. In both cases generic rules may still block it.

HTML: https://cve.vigilbase.com/cve/CVE-2022-0403 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2022-0403