LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25400: WordPress Apicona theme <= 24.1.0 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in thememount Apicona apicona allows Object Injection.This issue affects Apicona: from n/a through <= 24.1.0.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-25400 affects the WordPress Apicona theme through version 24.1.0. It is a PHP object injection issue caused by unsafe deserialization. If exploited by a logged-in attacker, it could allow serious compromise of the site’s data, integrity, or availability.

Executive priority

Treat as high priority for WordPress sites using Apicona, especially public sites with user accounts. The issue has severe potential impact, but the supplied sources do not confirm active exploitation or name a fixed version.

Technical view

The vulnerability is CWE-502 deserialization of untrusted data in thememount Apicona. CVSS 3.1 is 8.8, vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. The source bundle identifies affected Apicona versions through 24.1.0. No exploit details or confirmed fixed version are provided in the supplied sources.

Likely exposure

Exposure is limited to WordPress installations using the Apicona theme at version 24.1.0 or earlier. Sites without this theme are not indicated as affected by the supplied sources.

Exploitation context

The CVSS vector indicates exploitation is network-reachable, low complexity, requires low privileges, and needs no user interaction. CISA KEV status is false in the bundle, and no cited source confirms active exploitation.

Researcher notes

Focus validation on affected theme presence, version, and vendor remediation status. The key technical issue is unsafe PHP object deserialization. Impact may depend on reachable code paths and available object chains, which are not detailed in the provided sources.

Mitigation direction

  • Inventory WordPress sites for the Apicona theme and record installed versions.
  • Prioritize sites running Apicona version 24.1.0 or earlier.
  • Check ThemeMount, Patchstack, or WordPress theme distribution guidance for a fixed release.
  • Update the theme when a vendor-supported fixed version is available.
  • If no fix is available, consider disabling or replacing the theme based on business risk.

Validation and detection

  • Confirm whether Apicona is installed on each WordPress instance.
  • Verify the installed Apicona version is greater than 24.1.0 or otherwise vendor-confirmed safe.
  • Review vendor and Patchstack advisories for remediation updates.
  • Assess whether low-privileged accounts exist on exposed affected sites.
  • Monitor affected sites for unusual authenticated activity or unexpected theme-related errors.
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-25400 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-25400Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
thememountApiconaapicona, 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.