VYPR
Unrated severityNVD Advisory· Published Jun 16, 2026

WordPress Mr. SEO theme <= 2.0 - Local File Inclusion vulnerability

CVE-2026-39568

Description

Unauthenticated Local File Inclusion in Mr. SEO theme versions <= 2.0 allows attackers to read sensitive files.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Unauthenticated Local File Inclusion in Mr. SEO theme versions <= 2.0 allows attackers to read sensitive files.

Vulnerability

The Mr. SEO WordPress theme versions 2.0 and earlier contain an unauthenticated Local File Inclusion (LFI) vulnerability. An attacker can include arbitrary local files from the server without requiring any authentication or user interaction. The vulnerability is present in the theme's file handling logic, allowing inclusion of files such as configuration files containing database credentials. [1]

Exploitation

An attacker can exploit this vulnerability by sending a crafted HTTP request to the vulnerable endpoint. No authentication is needed, and the attack can be performed remotely over the network. The attacker simply needs to manipulate a parameter that controls file inclusion to point to a local file path. The file's contents are then displayed in the response. [1]

Impact

Successful exploitation allows an unauthenticated attacker to read sensitive local files from the server, including files that store database credentials. This could lead to complete database compromise depending on the server configuration. The vulnerability is considered highly dangerous and is expected to be used in mass-exploit campaigns targeting thousands of websites. [1]

Mitigation

The vulnerability is fixed in version 2.1 of the Mr. SEO theme. Users are advised to update to version 2.1 or later immediately. If unable to update, a mitigation rule is available from Patchstack to block attacks until the update is applied. [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

2

Patches

0

No 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

1

News mentions

1