LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27082: WordPress Love Story theme <= 1.3.12 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in ThemeREX Love Story lovestory allows Object Injection.This issue affects Love Story: from n/a through <= 1.3.12.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-27082 is a critical flaw in the WordPress Love Story theme by ThemeREX, affecting versions through 1.3.12. A remote unauthenticated attacker may be able to trigger unsafe PHP object deserialization, risking full compromise of confidentiality, integrity, and availability. No cited source confirms active exploitation.

Executive priority

Treat this as urgent for any internet-facing WordPress site using Love Story. The potential impact is severe, and exploitation does not require authentication per CVSS. Priority should focus on confirming usage, removing exposure where possible, and tracking official remediation.

Technical view

The issue is CWE-502, deserialization of untrusted data, leading to PHP Object Injection in the Love Story theme package “lovestory.” The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction required. Public details do not name a patched version or safe configuration.

Likely exposure

Exposure is likely limited to WordPress sites using the ThemeREX Love Story theme at version 1.3.12 or earlier. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation may be possible without user interaction. However, the source bundle does not provide exploit details, proof-of-concept status, or evidence of exploitation in the wild. It is not listed as KEV in the provided data.

Researcher notes

Public information is sparse. The CVE and Patchstack entry identify PHP Object Injection via unsafe deserialization but do not provide technical root cause, affected code path, exploit prerequisites beyond CVSS, or a named fixed release in the supplied data.

Mitigation direction

  • Inventory WordPress sites for the Love Story theme and installed version.
  • If installed and unnecessary, disable or remove the theme.
  • Check ThemeREX and Patchstack guidance for a fixed version or official workaround.
  • Prioritize compensating monitoring for affected public-facing WordPress sites.

Validation and detection

  • Confirm whether the Love Story theme is installed on each WordPress site.
  • Record the theme version and compare it to 1.3.12 or earlier.
  • Review vendor and Patchstack advisories for updated remediation status.
  • Check security logs for unusual requests or WordPress integrity changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2026-27082 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-27082Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXLove Storylovestory, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

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.