LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68910: WordPress Blogzee theme <= 1.0.5 - Arbitrary File Upload vulnerability

Unrestricted Upload of File with Dangerous Type vulnerability in blazethemes Blogzee blogzee allows Using Malicious Files.This issue affects Blogzee: from n/a through <= 1.0.5.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-68910 affects the WordPress Blogzee theme through version 1.0.5. It allows a logged-in user to upload dangerous file types. If abused, this can threaten site confidentiality, integrity, and availability. The published CVSS score is 9.9, so exposed sites should be treated as urgent.

Executive priority

Treat this as urgent for any public WordPress site running Blogzee through 1.0.5, especially if multiple users can log in. If the theme is not present, business risk from this CVE is low. If present, contain exposure until vendor guidance confirms remediation.

Technical view

The issue is CWE-434: unrestricted upload of a file with a dangerous type in blazethemes Blogzee. The CVSS vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, meaning network-accessible exploitation by a low-privileged authenticated user without user interaction. Provided sources do not name a fixed version.

Likely exposure

WordPress installations using the Blogzee theme version 1.0.5 or earlier are in scope. Exposure is higher where untrusted or lightly vetted users can authenticate to WordPress. The source bundle lists Blogzee default status as unaffected outside the specified affected range.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not listed as KEV in the bundle. The vulnerability class is high-impact because dangerous uploads can enable malicious file placement on a web application, but the exact exploit path is not detailed in the sources.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. The sources identify arbitrary dangerous file upload and CVSS 9.9 but do not provide a fixed version, exploit proof, or active exploitation evidence. Validate exposure through theme inventory and version checks rather than assumptions.

Mitigation direction

  • Identify WordPress sites using the Blogzee theme.
  • If Blogzee is version 1.0.5 or earlier, prioritize containment.
  • Remove or disable Blogzee where business impact allows.
  • Restrict WordPress accounts to trusted users only.
  • Check vendor and Patchstack guidance for a fixed release or official workaround.
  • Review sites for unexpected uploaded or modified executable files.

Validation and detection

  • Inventory installed WordPress themes and record Blogzee versions.
  • Confirm whether any instance is version 1.0.5 or earlier.
  • Review WordPress user roles for low-privileged authenticated access.
  • Check file integrity against known-good site backups.
  • Monitor Patchstack and CVE records for updated remediation details.
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-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-68910 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.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2025-68910Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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
blazethemesBlogzeeblogzee, 0unaffected
Weakness

CWE details

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

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.