Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-27412 – Unauthenticated Local File Inclusion – Pearl Corporate Business WordPress Theme …

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-27412 is a high-severity Unauthenticated Local File Inclusion (LFI) vulnerability in the Pearl – Corporate Business WordPress theme by StylemixThemes, affecting all versions up to and including 3.4.10. The flaw arises from improper control of filenames used in PHP include/require statements (CWE-98), allowing an unauthenticated remote attacker to include and expose arbitrary local files from the server. With a CVSS v3.1 score of 8.1 (High), the vulnerability carries a full-triad impact on confidentiality, integrity, and availability.

Technical details

  • Root cause: Improper control of filenames for PHP include/require statements (CWE-98); attacker-controlled input is passed to a file-inclusion function without adequate sanitization or path restriction, enabling traversal and loading of arbitrary local files.
  • Trigger conditions: No authentication or user interaction is required. The vulnerability is rated AC:H (High Attack Complexity), indicating that specific preconditions on the target environment must be met for successful exploitation.
  • Attack vector: Network-accessible; exploitable remotely over HTTP/HTTPS without any local access to the server.
  • Impact: Successful exploitation allows an attacker to read arbitrary local files from the server — including sensitive configuration files such as wp-config.php (which contains database credentials) and system files such as /etc/passwd. LFI vulnerabilities of this class can be further escalated toward Remote Code Execution (RCE) via PHP stream wrappers or server log poisoning, depending on server configuration.

Affected software

  • Pearl – Corporate Business WordPress Theme by StylemixThemes — versions ≤ 3.4.10

Severity

CVSS v3.1 Base Score: 8.1 (High)
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Update: No official vendor-confirmed security patch has been published at the time of this writing. Users should update to the latest available release of the theme and monitor the StylemixThemes Pearl changelog for a formal security fix.
  • Workaround: If an immediate update is not possible, restrict public HTTP access to the WordPress installation at the network or hosting layer. Review and harden PHP include paths via open_basedir restrictions in the server configuration to limit the directories accessible to PHP file-inclusion calls.
  • Network mitigation: Deploy a Web Application Firewall (WAF) rule targeting LFI traversal patterns (e.g., ../, PHP wrapper prefixes such as php://, file://) in HTTP request parameters directed at the theme’s endpoints.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge