LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32509: WordPress Gracey theme < 1.4 - Arbitrary Object Instantiation vulnerability

Deserialization of Untrusted Data vulnerability in Edge-Themes Gracey gracey allows Object Injection.This issue affects Gracey: from n/a through < 1.4.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32509 affects the WordPress Gracey theme before version 1.4. A logged-in attacker may be able to abuse unsafe data deserialization to instantiate objects, potentially causing limited site integrity or availability impact. Public sources rate this medium severity, and there is no cited evidence of active exploitation.

Executive priority

Treat as a routine but timely WordPress maintenance item. Prioritize public-facing sites running Gracey with many user accounts or weak account governance. The issue is not currently supported as actively exploited by the provided sources, but outdated themes remain a common operational risk.

Technical view

The issue is CWE-502 deserialization of untrusted data in Edge-Themes Gracey. The CVSS 3.1 score is 5.4 with AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L. Affected versions are Gracey before 1.4. Available sources do not describe the vulnerable endpoint, required role, gadget conditions, or proof-of-concept details.

Likely exposure

Exposure is limited to WordPress sites using the Edge-Themes Gracey theme below version 1.4. The CVSS vector indicates remote network access is possible, but attacker privileges are required. Sites not using Gracey, or running version 1.4 or later, are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. The vulnerability requires low privileges and no user interaction. Practical impact may depend on site configuration and available object chains, but those details are not provided in the sources.

Researcher notes

Public detail is sparse. The record identifies object injection through unsafe deserialization but does not provide sink location, trigger conditions, minimum role, or exploitability constraints. Validation should focus on confirmed version exposure and vendor/Patchstack advisories, not assumed exploit paths.

Mitigation direction

  • Update the Gracey theme to version 1.4 or later if available.
  • Confirm remediation guidance with Patchstack or the theme vendor.
  • Remove the Gracey theme from sites where it is not needed.
  • Review and reduce unnecessary WordPress user accounts and privileges.

Validation and detection

  • Inventory WordPress sites for the Gracey theme.
  • Check installed Gracey versions and flag anything below 1.4.
  • Verify the updated theme remains active and site functionality is normal.
  • Monitor authenticated WordPress activity for unusual changes or errors.
Prepared
Confidence
high
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-32509 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-32509Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Edge-ThemesGraceygracey, n/aunaffected
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.