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

New CVE Detected

CVE-2026-78572 – PHP Object Injection – Kalles Addons WordPress Plugin (≤ 1.0.6)

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

Summary

CVE-2026-78572 is a PHP Object Injection vulnerability (CWE-502) in the Kalles Addons plugin for WordPress, affecting all versions up to and including 1.0.6. The flaw stems from deserialization of untrusted input and allows unauthenticated attackers to inject arbitrary PHP objects. The issue carries a CVSS v3.1 score of 8.1 (High).

Technical details

  • Root cause: The plugin deserializes untrusted, attacker-controlled input without adequate validation, enabling PHP Object Injection.
  • Trigger conditions: No authentication is required; an attacker can submit crafted serialized data to a vulnerable endpoint exposed by the plugin.
  • Attack vector: Network — exploitable remotely over HTTP(S) against any internet-facing WordPress site running the vulnerable plugin.
  • Impact: No Property-Oriented Programming (POP) chain exists within Kalles Addons itself, so the injected object alone has no direct effect. However, if the target site also runs another plugin or theme containing an exploitable POP chain, an attacker could leverage the combination to delete arbitrary files, access sensitive information, or execute arbitrary code.

Affected software

  • Kalles Addons WordPress plugin: all versions up to and including 1.0.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 Kalles Addons to a version newer than 1.0.6 that resolves the deserialization issue.
  • If no patch is available: Audit all installed plugins and themes for known POP chains, remove or update any that could be chained with this vulnerability, and restrict access to the plugin’s endpoints via a web application firewall until patched.
  • Monitor site integrity and logs for unexpected serialized-data submissions or unauthorized file changes as a precaution.

How IONIX identifies potentially affected assets

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

  • Raw response body: /wp-content/plugins/kalles-addons

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge