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

Back
New CVE Detected

CVE-2026-78032 – Remote Code Execution via Insecure Deserialization – SOY CMS ≤ 3.24.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-78032 is a critical deserialization-of-untrusted-data vulnerability (CWE-502) affecting SOY CMS, an open-source content management system developed by Tsuyoshi Saito. The flaw allows an unauthenticated remote attacker to submit crafted serialized data to the application, resulting in arbitrary code execution with the privileges of the web server process. The issue carries a CVSS v3.0 base score of 9.8 (Critical) and a CVSS v4.0 score of 9.3 (Critical), reflecting its network-exploitable, low-complexity, no-authentication attack path.

Technical details

  • Root cause: SOY CMS deserializes untrusted, attacker-supplied input without adequate validation or type restriction (CWE-502 – Deserialization of Untrusted Data).
  • Trigger conditions: An attacker sends specially crafted serialized data to a vulnerable SOY CMS endpoint; no authentication or user interaction is required. The issue affects installations running PHP 7.0 or later.
  • Attack vector: Network — remotely exploitable over HTTP(S) with low attack complexity and no privileges or user interaction required.
  • Impact: Successful exploitation allows execution of arbitrary PHP/OS-level code in the context of the web server, which can lead to full compromise of confidentiality, integrity, and availability of the affected host.

Affected software

  • SOY CMS — version 3.24.0 and earlier

Severity

  • CVSS v3.0 Base Score: 9.8 (Critical) — CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Score: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade SOY CMS to version 3.25.0 or later, which the vendor has confirmed remediates the deserialization flaw along with related cross-site scripting issues in the SOY product line.
  • If immediate patching is not possible:
    • Restrict network access to SOY CMS administration and application endpoints to trusted IP ranges via firewall or reverse-proxy ACLs.
    • Place a web application firewall (WAF) in front of the application to detect and block anomalous serialized-object payloads.
    • Monitor web server and application logs for unusual POST payloads or unexpected process execution originating from the web server user.
    • Isolate the CMS host/container from sensitive internal network segments to limit blast radius if compromised.

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