Security Resilience

CVE-2025-46474

Published
23 May 2025
Modified
17 June 2026
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0080 56th percentile
Risk Priority 63 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-46474 is a high-severity PHP Remote File Inclusion (CWE-98) vulnerability. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-46474 is a PHP Local File Inclusion vulnerability, tracked under CWE-98, that stems from improper control of filenames in include or require statements. It affects the SEUR Oficial WordPress plugin, versions from n/a through 2.2.23, and carries a CVSS 3.1 score of 8.1 reflecting network attack vector, high complexity, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability.

An unauthenticated remote attacker can exploit the flaw over the network to include and execute arbitrary local files on the server. Successful exploitation can lead to disclosure of sensitive information, modification of application behavior, or full compromise of the affected WordPress site.

The vulnerability is documented in the Patchstack database, which lists the affected plugin versions and provides the primary advisory reference for further details on detection and remediation. The associated EPSS score remains flat at 0.0206 with no material increase observed since disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in SEUR OFICIAL SEUR Oficial seur allows PHP Local File Inclusion.This issue affects SEUR Oficial: from n/a through <= 2.2.23.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-52807Shared CWE-98
CVE-2025-64360Shared CWE-98
CVE-2025-58215Shared CWE-98
CVE-2026-27988Shared CWE-98
CVE-2025-52728Shared CWE-98
CVE-2026-28096Shared CWE-98
CVE-2025-60194Shared CWE-98
CVE-2026-0926Shared CWE-98
CVE-2026-92174Shared CWE-98
CVE-2026-22442Shared CWE-98

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and static analysis can discover missing filename restrictions before deployment.

Validating all inputs before they reach include/require statements directly stops untrusted filenames from being used.

Enforcing access authorizations on resources limits what an included file can reach even if a bad name is supplied.

Information-flow rules can block the loading of external or unauthorized files into the PHP process.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.

PR.PS-01 partial match
blocks

Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.

PR.PS-05 partial match
blocks

Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect RFI but does not prevent the weakness by itself.

prevents

Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.

References