WordPress Wanium theme <= 1.9.8 - Local File Inclusion vulnerability
Description
Unauthenticated Local File Inclusion (LFI) in Wanium theme <=1.9.8 allows remote attackers to read sensitive files, risking credential exposure and data breach.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Unauthenticated Local File Inclusion (LFI) in Wanium theme <=1.9.8 allows remote attackers to read sensitive files, risking credential exposure and data breach.
Vulnerability
Wanium, a WordPress theme, suffers from an unauthenticated Local File Inclusion (LFI) vulnerability in versions up to and including 1.9.8. The flaw enables an attacker to include arbitrary local files from the server without requiring authentication, allowing them to read the contents of sensitive files such as wp-config.php which stores database credentials [1].
Exploitation
An attacker with network access to a WordPress site running an affected Wanium theme version can exploit this vulnerability remotely without authentication or user interaction. The attack vector is network-based, and no special privileges are needed. The exploitation steps are not detailed publicly but involve sending crafted requests to the vulnerable parameter, resulting in the inclusion of arbitrary local files [1].
Impact
Successful exploitation leads to disclosure of sensitive information, including database credentials, configuration files, and other local files. This can compromise the confidentiality of the entire WordPress installation and potentially lead to complete database takeover if credentials are exposed. The vulnerability has a CVSS score of 8.1 (High) and is considered highly dangerous, expected to be used in mass-exploit campaigns targeting thousands of websites regardless of size or popularity [1].
Mitigation
An immediate update to the latest secure version of the Wanium theme is required. If unavailable, users should contact their hosting provider or web developer for assistance. As of the published date, no fixed version is mentioned in the available references [1].
AI Insight generated on Jun 17, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
1- Wordfence Intelligence Weekly WordPress Vulnerability Report (May 25, 2026 to May 31, 2026)Wordfence Blog · Jun 4, 2026