VYPR
Critical severity9.8NVD Advisory· Published Aug 13, 2025· Updated Apr 15, 2026

CVE-2025-6715

CVE-2025-6715

Description

The LatePoint WordPress plugin before 5.1.94 is vulnerable to Local File Inclusion via the layout parameter. This makes it possible for attackers to include and execute PHP files on the server, allowing the execution of any PHP code in those files.

AI Insight

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

Unauthenticated Local File Inclusion in LatePoint WordPress plugin before 5.1.94 allows arbitrary PHP file execution via the layout parameter.

The LatePoint WordPress plugin, versions before 5.1.94, is vulnerable to an unauthenticated Local File Inclusion (LFI) flaw through the layout parameter. This vulnerability, reported as critical with a CVSS score of 9.8, allows an attacker to include arbitrary files from the server [1]. By controlling the layout parameter, an attacker can include a PHP file, and if the included file contains PHP code, that code will be executed on the server [1].

No authentication is required to exploit this vulnerability, making it accessible to any remote attacker. The attack surface is direct; an attacker simply needs to craft a request to the vulnerable plugin with a malicious value for the layout parameter [1]. The proof of concept demonstrates that this can be done without any prior access to the WordPress site [1].

The impact of successful exploitation is severe. An attacker can achieve remote code execution by including a PHP file that contains malicious code, such as a web shell [1]. This could lead to full site compromise, including data theft, privilege escalation, and further attacks on the server infrastructure. The vulnerability affects the core functionality of the plugin, and a proof of concept has been publicly disclosed, increasing the risk of exploitation [1].

The vulnerability has been fixed in version 5.1.94 of the LatePoint plugin [1]. Users are strongly advised to update to this patched version immediately. As of the publication date, no known workarounds have been provided, so updating is the primary mitigation [1].

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

1

News mentions

0

No linked articles in our index yet.