LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32511: WordPress Stål theme < 1.7 - Arbitrary Object Instantiation vulnerability

Deserialization of Untrusted Data vulnerability in Mikado-Themes Stål stal allows Object Injection.This issue affects Stål: from n/a through < 1.7.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32511 affects the WordPress Stål theme before version 1.7. An authenticated attacker with low privileges may trigger unsafe deserialization, causing limited site integrity and availability impact. This is not marked as known exploited in KEV, but exposed WordPress sites using the vulnerable theme should be updated promptly.

Executive priority

Treat as a timely WordPress maintenance item, not an emergency absent exploitation evidence. Prioritize internet-facing or multi-user WordPress sites using Stål, especially where untrusted users can log in.

Technical view

The issue is CWE-502, deserialization of untrusted data, described as arbitrary object instantiation/object injection in Mikado-Themes Stål. CVSS 3.1 is 5.4: network attack vector, low complexity, low privileges required, no user interaction, with low integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is limited to WordPress installations using the Mikado-Themes Stål theme below version 1.7. The CVSS vector indicates exploitation requires a low-privileged authenticated account, reducing risk versus unauthenticated flaws but still relevant for membership, contributor, customer, or multi-user sites.

Exploitation context

No provided source states active exploitation, and the CVE is not listed as KEV. Public information identifies the vulnerability class and affected version range, but does not provide detailed exploitation conditions beyond the CVSS requirements.

Researcher notes

Sources do not include a vendor advisory, proof of concept, or detailed sink/source analysis. Assessment relies on CVE metadata and Patchstack’s vulnerability entry. Validate exposure by theme version and authentication model, and avoid assuming impact beyond CVSS-stated low integrity and availability effects.

Mitigation direction

  • Update the Stål WordPress theme to version 1.7 or later.
  • If updating is not possible, check Patchstack or vendor guidance for temporary mitigations.
  • Restrict or review low-privileged WordPress accounts until remediation is complete.
  • Back up the site before theme updates and test in staging where possible.

Validation and detection

  • Inventory WordPress sites for the Stål theme.
  • Confirm installed Stål theme version is 1.7 or later.
  • Review whether low-privileged user registration or access is enabled.
  • Check security tooling or Patchstack coverage for CVE-2026-32511 detection.
  • Verify no unexpected theme modifications remain after updating.
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-32511 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-32511Attack 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
Mikado-ThemesStålstal, 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.