LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69004: WordPress Bajaar - Highly Customizable WooCommerce WordPress Theme theme <= 2.1.0 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in XpeedStudio Bajaar - Highly Customizable WooCommerce WordPress Theme bajaar allows PHP Local File Inclusion.This issue affects Bajaar - Highly Customizable WooCommerce WordPress Theme: from n/a through <= 2.1.0.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69004 is a high-severity file inclusion issue in the WordPress Bajaar WooCommerce theme from XpeedStudio, affecting versions through 2.1.0. A successful attack could let an unauthenticated remote attacker impact confidentiality, integrity, and availability. Public sources do not indicate known active exploitation.

Executive priority

Prioritize remediation for any public WooCommerce site running Bajaar through 2.1.0. The issue is high severity and could affect sensitive site data or availability, but current provided sources do not show confirmed exploitation in the wild.

Technical view

The CVE describes improper control of a filename used in a PHP include/require statement, mapped to CWE-98, resulting in PHP local file inclusion. The CVSS v3.1 score is 8.1 with network attack vector, high complexity, no privileges, and no user interaction required.

Likely exposure

Exposure is likely limited to WordPress sites using the Bajaar - Highly Customizable WooCommerce WordPress Theme at version 2.1.0 or earlier. Internet-facing WooCommerce stores using this theme should be prioritized because compromise could affect customer-facing commerce infrastructure.

Exploitation context

The CVE record and Patchstack reference classify this as local file inclusion. The CVSS vector indicates unauthenticated remote reachability but high attack complexity. CISA KEV status is false in the provided bundle, and no cited source confirms active exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The affected-version data in the bundle includes both a narrative range through 2.1.0 and an affected entry listing version “0”; rely on vendor/Patchstack validation before final scoping.

Mitigation direction

  • Identify any WordPress sites using the Bajaar theme.
  • If Bajaar is present and <=2.1.0, treat the site as exposed.
  • Check XpeedStudio and Patchstack guidance for an official fix or mitigation.
  • Update, replace, or disable the affected theme per vendor guidance.
  • Apply compensating monitoring and access controls until remediation is complete.

Validation and detection

  • Inventory installed WordPress themes across production and staging sites.
  • Confirm Bajaar theme version from WordPress administration or asset records.
  • Compare findings against the affected range: through version 2.1.0.
  • Review web and application logs for unusual file access patterns.
  • Document remediation status for each affected site.
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 · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2025-69004 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.1 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2025-69004Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/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
XpeedStudioBajaar - Highly Customizable WooCommerce WordPress Themebajaar, 0unaffected
Weakness

CWE details

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

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.