Lekker
Monthly
We need to produce a JSON with specific fields about CVE-2025-69034. Input data: CVE ID, description, CVSS score 8.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')), EPSS 0.06% (20% percentile), reported by audit@patchstack.com, CPE: cpe:2.3:a:qodeinteractive:lekker:*:*:*:*:*:wordpress:*:*, tags: Information Disclosure, PHP, LFI, Lekker, references: nvd link but it says (None) and then a patchstack URL. Actually, the references say: [nvd] (None) https://patchstack.com/database/Wordpress/Theme/lekker/vulnerability/wordpress-lekker-theme-1-8-local-file-inclusion-vulnerability?_s_id=cve. That seems to be a single reference from Patchstack. No indication of KEV status, POC availability, patch availability, etc. So we must synthesize based on given data. We'll need to infer from description: "Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes Lekker lekker allows PHP Local File Inclusion. This issue affects Lekker: from n/a through <= 1.8." Mikado-Themes? Actually the vendor in CPE is qodeinteractive, that might be the parent. So product name: Lekker (WordPress theme). "Lekker" appears twice. Fields: product_name: "Lekker" (1-3 words, specific product). Could say "Lekker WordPress Theme". I'll do "Lekker Theme" or "Lekker (WordPress)". Rules: 1-3 words. I'll go with "Lekker Theme". summary: Avoid starting with "A vulnerability...". Start with impact verb and product: "Local file inclusion in the Lekker WordPress theme (versions ≤ 1.8) allows unauthenticated remote attackers to read arbitrary files on the server, potentially leading to sensitive data exposure and code execution." The description says "PHP Remote File Inclusion" but then says "allows PHP Local File Inclusion". So it's LFI. Exploitation status: no public exploit identified. EPSS is very low (0.06%), 20t
We need to produce a JSON with specific fields about CVE-2025-69034. Input data: CVE ID, description, CVSS score 8.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')), EPSS 0.06% (20% percentile), reported by audit@patchstack.com, CPE: cpe:2.3:a:qodeinteractive:lekker:*:*:*:*:*:wordpress:*:*, tags: Information Disclosure, PHP, LFI, Lekker, references: nvd link but it says (None) and then a patchstack URL. Actually, the references say: [nvd] (None) https://patchstack.com/database/Wordpress/Theme/lekker/vulnerability/wordpress-lekker-theme-1-8-local-file-inclusion-vulnerability?_s_id=cve. That seems to be a single reference from Patchstack. No indication of KEV status, POC availability, patch availability, etc. So we must synthesize based on given data. We'll need to infer from description: "Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes Lekker lekker allows PHP Local File Inclusion. This issue affects Lekker: from n/a through <= 1.8." Mikado-Themes? Actually the vendor in CPE is qodeinteractive, that might be the parent. So product name: Lekker (WordPress theme). "Lekker" appears twice. Fields: product_name: "Lekker" (1-3 words, specific product). Could say "Lekker WordPress Theme". I'll do "Lekker Theme" or "Lekker (WordPress)". Rules: 1-3 words. I'll go with "Lekker Theme". summary: Avoid starting with "A vulnerability...". Start with impact verb and product: "Local file inclusion in the Lekker WordPress theme (versions ≤ 1.8) allows unauthenticated remote attackers to read arbitrary files on the server, potentially leading to sensitive data exposure and code execution." The description says "PHP Remote File Inclusion" but then says "allows PHP Local File Inclusion". So it's LFI. Exploitation status: no public exploit identified. EPSS is very low (0.06%), 20t