LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69148: WordPress Quirky theme <= 1.23 - Local File Inclusion vulnerability

Unauthenticated Local File Inclusion in Quirky <= 1.23 versions.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue affects WordPress sites using the ThemeREX Quirky theme up to version 1.23. An unauthenticated attacker may be able to make the site include local files, which can expose sensitive data or affect site integrity. The public record rates it high severity, but exploitation requires high attack complexity.

Executive priority

Treat as a high-priority WordPress exposure for any site running Quirky <= 1.23, especially internet-facing sites. Prioritize inventory first because the bundle lacks exact affected package metadata and does not confirm a patch.

Technical view

CVE-2025-69148 is an unauthenticated Local File Inclusion issue in Quirky <= 1.23, mapped to CWE-98. The CVSS 3.1 score is 8.1 with network attack vector, no privileges or user interaction required, high complexity, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress installations using the ThemeREX Quirky theme at version 1.23 or earlier. The source bundle does not provide CPEs, exact package metadata, or deployment prevalence, so asset inventory is required.

Exploitation context

The bundle does not cite active exploitation, and KEV status is false. Public evidence supports a high-severity unauthenticated LFI risk, but the CVSS vector marks attack complexity as high. No exploit details are needed to validate exposure.

Researcher notes

The affected section lists version data as n/a while the title and description state <= 1.23. Use the CVE and Patchstack entries as source anchors, but verify vendor advisories before asserting a specific fixed version or remediation path.

Mitigation direction

  • Identify all WordPress sites using the ThemeREX Quirky theme.
  • Check ThemeREX and Patchstack guidance for a fixed version or vendor mitigation.
  • Update Quirky if a vendor-supported patched release is available.
  • Disable or replace the theme where no trusted fix is available.
  • Review WAF or virtual patching options from trusted vendor guidance.

Validation and detection

  • Confirm installed Quirky theme versions across production, staging, and backups.
  • Verify whether any site runs Quirky version 1.23 or earlier.
  • Review web and PHP error logs for suspicious file inclusion behavior.
  • Check whether sensitive local files were exposed in responses or logs.
  • Document compensating controls and remaining unpatched instances.
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-69148 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
3Timeline 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.9Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2025-69148Attack 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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXQuirkyquirky, n/aunaffected
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.