# CVE-2022-4063: InPost Gallery < 2.1.4.1 - Unauthenticated LFI to RCE - Exploited (CISA KEV): no - Published: 2022-12-19 - CVSS: 9.8 CRITICAL (v3.1) - EPSS: 10.2% (96th percentile) The InPost Gallery WordPress plugin before 2.1.4.1 insecurely uses PHP's extract() function when rendering HTML views, allowing attackers to force the inclusion of malicious files & URLs, which may enable them to run code on servers. ## 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 | 2024-03-12 | 449 | | Akamai | No public source | — | — | | OWASP CRS | No public claim | — | — | ### F5 - 2024-03-12 · new · rule 200009301 > Added: signature 200009301 "WordPress InPost Gallery Local File Inclusion" (Information Leakage, risk High), systems: PHP, WordPress. References: CVE-2022-4063. Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog - 2024-05-21 · new · rule 200009301 > Added: signature 200009301 "WordPress InPost Gallery Local File Inclusion" (Information Leakage, risk High), systems: PHP, WordPress. References: CVE-2022-4063. Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog ## Our test (measured) - OWASP Core Rule Set 4.25.0, paranoia level 1, anomaly threshold 5, default CRS settings: passed (0 of 1 requests blocked), template CVE-2022-4063, 2026-11-02 - OWASP Core Rule Set 4.25.0, paranoia level 2, anomaly threshold 5, default CRS settings: blocked (1 of 1 requests blocked), template CVE-2022-4063, 2026-11-02 "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-4063 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2022-4063