Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress Deliciosa theme and may let an unauthenticated attacker include local files on a vulnerable site. The source rates it high severity. For executives, the concern is exposure of sensitive files and possible wider site compromise, but current sources do not show active exploitation.
Executive priority
Treat this as a near-term remediation item for any public WordPress site using Deliciosa. It is high severity and unauthenticated, but evidence of active exploitation is not present in the supplied sources.
Technical view
CVE-2025-69121 is an unauthenticated local file inclusion issue, mapped to CWE-98, in ThemeREX Deliciosa versions up to 1.10.0. CVSS 3.1 is 8.1 with network access, high attack complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
WordPress sites using the ThemeREX Deliciosa theme at version 1.10.0 or earlier are the likely exposure set. The provided data does not identify CPEs or package ecosystem metadata beyond the theme package name.
Exploitation context
The CVE is not listed as KEV in the source bundle, and no cited source states active exploitation. Attack complexity is rated high, but the issue is remotely reachable and unauthenticated if the vulnerable theme is present.
Researcher notes
The bundle provides CVSS, CWE-98, unauthenticated LFI classification, and affected theme boundary through <=1.10.0. It does not provide root-cause code details, a fixed version, exploit indicators, or confirmed exploitation telemetry.
Mitigation direction
Inventory WordPress sites for the Deliciosa theme and installed version.
Prioritize sites running Deliciosa version 1.10.0 or earlier.
Check ThemeREX and Patchstack guidance for a fixed release or virtual patch.
Apply the vendor-supported update when available.
Temporarily disable or replace the theme if no safe update is available.
Validation and detection
Confirm whether Deliciosa is installed on each WordPress site.
Record the exact theme version and compare it to 1.10.0.
Review vendor and Patchstack advisories for updated remediation status.
Check web logs for suspicious requests targeting theme files.
Verify backup and recovery readiness before changing production themes.
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.
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
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.
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.