Security readout for executives and security teams
Plain-English summary
Flatastic for WordPress is reported vulnerable to an unauthenticated PHP object injection flaw in versions through 2.0. A remote attacker may target an exposed site without credentials or user interaction. The supplied CVSS assessment indicates potentially severe confidentiality, integrity, and availability impact, but the sources do not describe confirmed outcomes for a specific site.
Executive priority
Treat confirmed internet-facing installations at version 2.0 or earlier as an immediate remediation priority. First establish whether Flatastic exists anywhere in production, including inactive theme copies. Escalate to incident response if suspicious activity or integrity changes appear. Active exploitation is not established by the supplied evidence.
Technical view
CVE-2026-66672 is classified as CWE-502: deserialization of untrusted data. The reported attack is network-accessible, low-complexity, unauthenticated, and requires no user interaction. Successful impact may depend on usable PHP classes or gadget chains in the installation; the supplied sources do not document the vulnerable input, prerequisites, proof of concept, or confirmed code execution.
Likely exposure
Internet-facing WordPress installations using Flatastic version 2.0 or earlier are the likely exposure group. The bundle’s description and title specify versions through 2.0, but its structured affected record lists versions as unavailable and defaults to unaffected. Confirm the installed theme and version directly rather than relying solely on automated CPE matching.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public exploit code, or observed attacks. Its 9.8 CVSS score reflects technical potential, not confirmed exploitation. Exposure should still be assessed promptly because the reported flaw is remotely reachable without authentication.
Researcher notes
The record is sparse and internally inconsistent: narrative fields identify Flatastic through 2.0, while structured affected data says version unavailable and defaults to unaffected. No vulnerable parameter, patch version, gadget chain, proof of concept, or exploitation telemetry is provided. Avoid asserting remote code execution or compromise without additional evidence.
Mitigation direction
- Check Patchstack and the theme vendor for current remediation guidance and a fixed release.
- Update to a vendor-confirmed safe version when one is identified.
- Disable or remove Flatastic if exposure cannot be promptly resolved.
- Restrict public access to affected sites if the theme must remain temporarily.
- Preserve backups and relevant logs before remediation or incident investigation.
Validation and detection
- Inventory WordPress sites for installed, active, or retained copies of Flatastic.
- Record the Flatastic version and flag installations at version 2.0 or earlier.
- Confirm remediation status against current vendor or Patchstack guidance.
- Review web and security logs for suspicious unauthenticated activity around affected sites.
- Perform integrity and account reviews if compromise indicators are discovered.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-66672 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/theme/flatastic/vulnerability/wordpress-flatastic-theme-2-0-php-object-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.