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

Back
New CVE Detected

CVE-2026-66650 – Unauthenticated PHP Object Injection – FreightCo WordPress Theme (≤ 1.1.15)

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-66650 is an unauthenticated PHP Object Injection (PHP Object Injection / Insecure Deserialization) vulnerability affecting the FreightCo WordPress theme by Theme-Rex, in versions up to and including 1.1.15. The flaw allows a remote, unauthenticated attacker to submit crafted serialized data that the theme deserializes without proper validation. It carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The theme deserializes untrusted, attacker-supplied input using PHP’s native deserialization functions without validating or sanitizing the data (CWE-502: Deserialization of Untrusted Data).
  • Trigger conditions: An attacker submits a specially crafted serialized PHP object to a theme endpoint or parameter that is later passed to a deserialization function.
  • Attack vector: Network-based, requiring no authentication and no user interaction, making the site directly exploitable by any remote actor.
  • Impact: Depending on other classes/gadget chains present on the target (in the theme, WordPress core, or other installed plugins), object injection can lead to arbitrary PHP object instantiation, and potentially to further impacts such as file deletion, data manipulation, or remote code execution — reflected in the high confidentiality, integrity, and availability impact of the CVSS vector.

Affected software

  • FreightCo WordPress theme (Theme-Rex) — all versions up to and including 1.1.15

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No fixed version has been publicly identified for this CVE at the time of writing. Site owners should check with Theme-Rex / the theme’s distribution channel (e.g. ThemeForest) for an updated release of FreightCo beyond 1.1.15 and apply it as soon as it becomes available.
  • If no patch is available:
    • Consider disabling or replacing the FreightCo theme until a fix is released.
    • Deploy a Web Application Firewall (WAF) rule to detect and block requests containing serialized PHP object payloads (e.g., strings beginning with O: or a: object/array serialization markers) directed at theme endpoints.
    • Restrict or monitor unauthenticated access to theme-specific AJAX/REST endpoints.
    • Review server and application logs for anomalous POST requests containing serialized data.

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/freightco/

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