Security readout for executives and security teams
Plain-English summary
CVE-2025-69172 is a high-severity unauthenticated local file inclusion issue in the WordPress Resurs theme versions up to 1.3. Affected public sites may expose sensitive files or suffer broader compromise depending on server configuration. The sources do not name a fixed version or confirmed exploitation.
Executive priority
Treat as urgent for any public WordPress site running Resurs <=1.3. Prioritize inventory first, then apply vendor guidance or remove exposure. Business urgency is high because the issue is unauthenticated and can affect confidentiality, integrity, and availability.
Technical view
The CVE describes CWE-98 in ThemeREX Resurs for WordPress, with CVSS 3.1 score 8.1 and network, no-authentication attack conditions. Attack complexity is high, but confidentiality, integrity, and availability impacts are rated high. Available sources identify Resurs <=1.3 but do not provide technical root cause or patch details.
Likely exposure
Exposure is most likely on internet-facing WordPress sites using the ThemeREX Resurs theme at version 1.3 or earlier. Sites not using this theme are not indicated as affected by the provided sources.
Exploitation context
The CVE is not listed as CISA KEV in the bundle, and no cited source confirms active exploitation. The vulnerability is remotely reachable and unauthenticated, but the CVSS vector rates attack complexity as high.
Researcher notes
Public evidence is sparse. The bundle identifies unauthenticated LFI, CWE-98, CVSS 8.1, and affected Resurs versions up to 1.3. It does not include vulnerable parameters, proof of exploitation, or a named fixed version, so validation should avoid assumptions beyond confirming theme presence and advisory updates.
Mitigation direction
Inventory WordPress sites for the Resurs theme and installed version.
Check ThemeREX and Patchstack for a fixed release or official mitigation.
Update Resurs if a vendor-fixed version is available.
Disable or replace affected themes where business impact permits.
Increase monitoring for suspicious file access or include-related requests.
Validation and detection
Confirm whether Resurs is installed on each WordPress instance.
Record the exact theme version and compare it with <=1.3 exposure.
Review vendor and Patchstack advisories for remediation status.
Check web logs for unusual local-file access patterns.
Verify backups and recovery plans for affected sites.
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
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.
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.