PatchSiren cyber security CVE debrief
CVE-2025-5804 Case Themes CVE debrief
A PHP Local File Inclusion vulnerability exists in Case Theme User, a WordPress plugin, due to improper control of filename for include/require statements. This issue affects Case Theme User versions from n/a through < 1.0.4. The vulnerability could lead to unauthorized access to local files or code execution. Defenders should verify exposure, apply patches or mitigations, and monitor for suspicious activity. The CVE record and NVD entry provide details, but additional information on exploitation or impact is limited.
- Vendor
- Case Themes
- Product
- Case Theme User
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-10
- Original CVE updated
- 2026-09-30
- Advisory published
- 2026-04-10
- Advisory updated
- 2026-09-30
Who should care
Defenders responsible for WordPress installations with the Case Theme User plugin should assess exposure and apply patches or mitigations to prevent potential local file inclusion attacks.
Why it matters
Defenders should care about CVE-2025-5804 because it involves a PHP Local File Inclusion vulnerability in the Case Theme User WordPress plugin, which could lead to unauthorized access to local files or code execution. The vulnerability affects versions from n/a through < 1.0.4, and defenders should verify exposure, apply patches or mitigations, and monitor for suspicious activity.
- Potential unauthorized access to local files
- Possible code execution through file inclusion
- Required verification of exposure and patch application
- Need for monitoring suspicious file inclusion attempts
Technical summary
The Case Theme User WordPress plugin is vulnerable to PHP Local File Inclusion due to improper control of filename for include/require statements. This issue affects versions from n/a through < 1.0.4. The vulnerability could lead to unauthorized access to local files or code execution. Defenders should prioritize verifying exposure and applying patches or mitigations to prevent potential local file inclusion attacks. The vulnerability has a high severity score of 7.5. Limited information is available on potential attacks or breaches.
Defensive priority
Defenders should prioritize verifying exposure and applying patches or mitigations to prevent potential local file inclusion attacks.
Recommended defensive actions
- Verify the version of Case Theme User and apply patches or updates to version 1.0.4 or later
- Restrict file inclusion to only trusted sources
- Monitor for suspicious file inclusion attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability. Additional information on exploitation or impact is limited. Defenders should verify exposure and apply patches or mitigations. The vulnerability affects Case Theme User versions from n/a through < 1.0.4. Limited information is available on potential attacks or breaches. Official sources indicate a high severity score of 7.5.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-5804 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-5804
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-5804 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-5804
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.