Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site using Kids Care theme ≤3.2.4
-
ExploitSend crafted request with manipulated path parameter
-
ExecutionTrigger PHP include of attacker-chosen local file
-
ImpactDisclose sensitive files and credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Command and Control The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The description specifies no explicit configuration prerequisite beyond running the Kids Care WordPress theme at version 3.2.4 or earlier; exploitation targets an unsanitized file-inclusion parameter and requires no authentication (PR:N) and no user interaction (UI:N). The principal LIMITING factor is the vendor-assigned High Attack Complexity (AC:H): a specific, non-trivial precondition or multi-step maneuver is required for reliable exploitation, though the available data does not name that precise condition (the exact vulnerable endpoint/parameter is not disclosed). Realistic impact is bounded by the attacker's inability to upload content in a classic LFI, so disclosure of readable local files (e.g., wp-config.php) is the most likely outcome unless a log-poisoning or wrapper technique enables escalation. |
| Impact | Signals are mixed and point to a credible but not top-tier priority. The CVSS 3.1 base score of 8.1 (High) reflects a network-reachable (AV:N), unauthenticated (PR:N), no-interaction (UI:N) flaw with full C/I/A impact, which on its face looks severe; however, the vendor-assigned High Attack Complexity (AC:H) is the key dampener, indicating a non-trivial precondition or specialized step is needed to succeed rather than trivial drive-by exploitation. No EPSS score was supplied, so statistical exploitation probability cannot be weighed. The CVE is NOT in CISA KEV (no active-exploitation signal) and no POC/exploit code is referenced, so exploitation status is 'no public exploit identified at time of analysis.' No SSVC decision data (automatable, technical impact) was provided. The C:H/I:H/A:H impact rating appears generous for a vulnerability the vendor tags as 'Information Disclosure / LFI' - pure local file inclusion is typically confidentiality-dominant, so the I:H/A:H components should be verified with Patchstack/the vendor. Net: a legitimately exploitable unauthenticated flaw worth patching, but the AC:H gate plus the absence of KEV/POC/EPSS suggests it is not currently under mass exploitation and ranks below trivially-exploitable AC:L internet-facing bugs. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker crafts a request to a vulnerable endpoint of a WordPress site running the Kids Care theme (<= 3.2.4) and abuses an unsanitized file-path parameter to force the PHP application to include a local file, disclosing sensitive content such as wp-config.php (database credentials, auth keys). The High attack complexity (AC:H) means success depends on a specific precondition or non-trivial step rather than a single trivial request. No public exploit code is referenced at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Local file inclusion in the Kids Care WordPress theme through version 3.2.4 allows unauthenticated remote attackers to manipulate a file-inclusion parameter and read local server files, with wp-config.php and other readable files as the primary exposure. The base CVSS vector is 8.1 with High Attack Complexity, but the independent assessment keeps the same unauthenticated and no-user-interaction prerequisites while bounding realistic impact to confidentiality-heavy local file disclosure with Low integrity and availability impact unless log poisoning or PHP wrappers enable escalation. No CISA KEV activity is identified in the provided data, and no public exploit identified at time of analysis; the independent assessment rates this as a credible but not top-tier priority.
RemediationAI
No vendor-released patch is identified in the provided data, so the primary mitigation is to remove or deactivate the Kids Care theme and replace it with a maintained theme; this eliminates the vulnerable include path but may require layout and template rework. If the theme cannot be removed immediately, deploy WAF or reverse-proxy rules that block path traversal and PHP stream-wrapper patterns such as ../, php://filter, and data:// in requests to theme PHP files, accepting that broad LFI signatures can cause false positives on legitimate requests; also harden PHP with open_basedir to restrict readable paths to the WordPress installation and expected upload directories, with the trade-off that overly tight paths can break plugins or theme features. Move wp-config.php above the webroot and minimize the web server user's filesystem read permissions to reduce the value of a successful LFI, but note these controls do not fix the underlying include flaw. Consult the Patchstack advisory for any updated vendor guidance: https://patchstack.com/database/wordpress/theme/kidscare/vulnerability/wordpress-kids-care-theme-3-2-4-local-file-inclusion-vulnerability?_s_id=cve.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-98 is the PHP include/require filename-control weakness class, usually described as PHP remote file inclusion, but in this case the reported behavior is local file inclusion through an unsanitized include parameter in the Kids Care WordPress theme by AxiomThemes. WordPress themes are PHP code executed directly by the web server, so a remote request can reach the vulnerable include path without authentication; the CPE cpe:2.3:a:axiomthemes:kids_care:*:*:*:*:*:*:*:* identifies the product, while the advisory and description bound the vulnerable versions to 3.2.4 and earlier. The independent assessment vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L confirms network reachability, no authentication, no user interaction, and High Attack Complexity for reliable exploitation, with realistic impact centered on local file disclosure rather than code execution; the vendor-facing vector lists Integrity High and Availability High, but the independent view bounds escalation because the attacker cannot upload content in a classic LFI, so wp-config.php or similar readable files are the most likely target unless log poisoning or PHP wrappers enable further impact. Tags confirm PHP, WordPress, information disclosure, and LFI, and the exact vulnerable endpoint and parameter are not disclosed in the provided data.
Know when Kids Care gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable unauthenticated LFI justifies AV:N/PR:N/UI:N; AC:H retained per vendor's specialized precondition; confidentiality-dominant (C:H) with limited integrity/availability since it is tagged information disclosure.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Kids Care <= 3.2.4 versions.
Executive ViewAI
The Kids Care WordPress theme, in versions through 3.2.4, contains a high-severity local file inclusion flaw that can expose sensitive server-side files such as wp-config.php to remote attackers. For organizations running this theme, the primary business concern is potential disclosure of database credentials, authentication salts, and other configuration secrets that could be used to pivot into broader WordPress or hosting compromise. No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis, so exposed sites require immediate scoping and risk reduction.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling or removing the Kids Care theme where possible, applying WAF or reverse-proxy virtual patching to block local file inclusion and path traversal against theme parameters, hardening file permissions so wp-config.php is not readable by the web server user, rotating database credentials and WordPress salts if exposure is suspected, and monitoring logs for file-read attempts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-96441
GHSA-q9qm-hg22-3w6v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB