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

Back
New CVE Detected

CVE-2026-28152 – Unauthenticated Local File Inclusion – Tonda Core (Tonda WordPress Theme) < 2.6

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-28152 is an unauthenticated Local File Inclusion (LFI) vulnerability in Tonda Core, the companion plugin bundled with the Tonda WordPress theme by Select-Themes. The flaw stems from improper control of filenames used in PHP include/require statements, allowing an attacker to influence which server-side files are loaded and executed. It carries a CVSS v3.1 base score of 8.1 (High) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: Improper control of filename for include/require statement in PHP (CWE-98) within Tonda Core.
  • Trigger conditions: An attacker-supplied value is passed into a PHP file inclusion routine without adequate validation or sanitization, allowing path/filename manipulation.
  • Attack vector: Network-based, unauthenticated; no privileges or user interaction required (attack complexity is rated High).
  • Impact: Successful exploitation can lead to disclosure of sensitive local files and, depending on server configuration, execution of arbitrary PHP code, with high impact to confidentiality, integrity, and availability of the affected site.

Affected software

  • Tonda Core (Select-Themes) — all versions prior to 2.6

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

  • Immediate: Update the Tonda Core plugin/theme component to version 2.6 or later, where the file inclusion handling has been fixed.
  • If immediate patching isn’t possible: Restrict direct web access to theme/plugin PHP files via web server rules, disable unused include-related functionality, and monitor for anomalous requests targeting theme file-loading parameters until the update can be applied.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/themes/tonda/

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