Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Pearl theme ≤3.4.10
-
DeliverySend crafted request with path/wrapper payload
-
ExploitReach unsanitized PHP include statement
-
ExecutionServer includes attacker-referenced local file
-
ImpactDisclose wp-config.php credentials and secrets
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 | Exploitation requires the target WordPress site to have the Pearl - Corporate Business theme (version ≤ 3.4.10) installed and active, and reachability of the specific theme endpoint/parameter that feeds the PHP include statement. No authentication is required (CVSS PR:N) and no user interaction is needed (UI:N), so any remote party who can reach the site over the network can attempt it. The principal limiting factor is the CVSS AC:H rating, which signals that a special condition beyond a trivial request - such as a particular encoding, path/wrapper form, or server configuration - must be met for reliable exploitation; the specific triggering parameter is not disclosed in the available data. Impact is bounded by PHP configuration (allow_url_include, open_basedir) which can constrain which local files are includable. |
| Impact | The signals are moderately strong but not top-tier urgent. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H = 8.1 High) indicates a network-reachable, unauthenticated flaw, which is a serious combination, but the AC:H metric materially lowers real-world exploitability by implying a non-trivial precondition or race/encoding hurdle rather than a trivial one-shot request. No EPSS probability was provided, so likelihood cannot be quantified from this data. The vulnerability is not on the CISA KEV list, and no proof-of-concept is referenced, so there is no evidence of active or automated exploitation. Note a tension in the vendor data: the tags label this 'Information Disclosure / LFI' (consistent with a read-only C:H impact), yet the official vector asserts I:H and A:H - for a pure LFI this is aggressive and likely reflects the theoretical include-to-execution ceiling of CWE-98 rather than confirmed integrity/availability impact; treat the I:H/A:H claims as unverified pending vendor detail. Overall this is a legitimate patch-soon item for sites running the Pearl theme, not a drop-everything emergency absent exploitation signals. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted HTTP request to a Pearl-theme WordPress site, supplying a manipulated path or PHP stream wrapper to a parameter that reaches an include/require call, causing the server to disclose the contents of wp-config.php and leak database credentials and secret keys. The AC:H rating suggests success may depend on specific encoding, path conditions, or configuration, so exploitation is plausible but not a guaranteed single request; no public proof-of-concept is currently referenced. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 02, 2026
Local File Inclusion in the Pearl - Corporate Business WordPress theme (StyleMixThemes) versions 3.4.10 and earlier lets unauthenticated remote attackers coerce the application into including arbitrary local files, exposing sensitive server-side content such as configuration files and credentials. Rated CVSS 8.1 by Patchstack, the flaw requires no authentication (PR:N) but carries high attack complexity (AC:H), and depending on include handling could escalate from information disclosure toward code execution. There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score supplied in the source data.
RemediationAI
No vendor-released patched version is identified in the provided data, so the specific fixed release cannot be cited with confidence - administrators should consult the Patchstack advisory (https://patchstack.com/database/wordpress/theme/pearl/vulnerability/wordpress-pearl-corporate-business-theme-3-4-10-local-file-inclusion-vulnerability) and the StyleMixThemes changelog for a version newer than 3.4.10 and upgrade to it as the primary fix. Until a confirmed patched build is applied, compensating controls include deploying a WAF or Patchstack virtual patch to block file-inclusion payloads (path traversal sequences like ../ and PHP wrappers such as php://filter and data:// against the theme's request parameters), hardening PHP by setting allow_url_include=Off and constraining open_basedir to the WordPress docroot so includes cannot reach sensitive files like /etc/passwd or /wp-config.php outside the web root (side effect: may break legitimate plugins that read outside the docroot), and restricting or disabling the vulnerable theme AJAX/endpoint if it can be identified. Where feasible, switching to a different maintained theme eliminates the exposure at the cost of site rework.
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
The affected component is a commercial WordPress theme, Pearl - Corporate Business, authored by StyleMixThemes (CPE cpe:2.3:a:stylemixthemes:pearl_-_corporate_business). The root cause maps to CWE-98, Improper Control of Filename for Include/Require Statement in a PHP Program - the classic PHP file-inclusion weakness where user-influenced input flows into an include(), require(), or equivalent statement without adequate validation or path canonicalization. In WordPress themes this typically arises from AJAX handlers, template loaders, or shortcode/parameter processing that build a filesystem path from a request parameter. Because PHP's include family both reads and can execute included content, this weakness class straddles pure information disclosure (reading /wp-config.php, /etc/passwd, log files) and, where an attacker can plant or reference includable PHP, remote code execution.
Know when Pearl Corporate Business 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
Unauthenticated network LFI (AV:N/PR:N) with AC:H per vendor precondition; assessed as read-only information disclosure so C:H but I:N/A:N absent confirmed code-execution or file-write.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Pearl - Corporate Business <= 3.4.10 versions.
Executive ViewAI
Organizations running the Pearl WordPress theme (versions 3.4.10 or earlier) face immediate exposure of sensitive credentials and configuration data to external attackers, creating direct risk of system compromise and data breach. No vendor patch is currently available, requiring urgent interim controls to minimize exploitation risk. This vulnerability demands prioritized response to protect critical business systems and customer data.
Deploy WAF rules blocking path traversal patterns and URL-encoded variants; implement restrictive file permissions on WordPress configuration files; restrict administrative access via IP allowlist or VPN; enable file access logging with alerts for suspicious inclusion attempts; consider temporary theme deactivation if other mitigations prove insufficient.
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-41331
GHSA-94cf-x5cw-j37q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB