S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated May 11, 2026

CVE-2025-48157 Scanner

CVE-2025-48157 Scanner - Local File Inclusion vulnerability in WordPress Formality Plugin

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.9k
Times Used
continuous scan runs
4.1k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2025-48157
8.1
CVSShigh
Exploitable remotely over the internet · no authentication required.

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Michele Giorgi Formality formality allows PHP Local File Inclusion.This issue affects Formality: from n/a through <= 1.5.9.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
Formalityby Michele Giorgi
0
Updated Aug 22, 2026View on NVD →
Detail

Formality is a plugin used with WordPress, a popular content management system used worldwide for creating and managing websites. Website developers and site administrators frequently use this plugin to add form management functionalities to their WordPress sites with ease. With its user-friendly interface and a variety of customization options, Formality facilitates easy handling of forms, making it an attractive choice for users ranging from individual bloggers to large corporations. Given its direct impact on a website's user interface and data management, maintaining its security is crucial. The software is utilized globally, affecting a wide range of users from different fields such as e-commerce, blogging, and corporate websites. Therefore, a vulnerability affecting this plugin can have widespread implications, necessitating vigilance and prompt updates.

Local File Inclusion (LFI) vulnerabilities occur when an attacker can manipulate input parameters to include files on a server. In this context, the vulnerability arises from a flaw in the plugin's code that improperly handles file paths within its include/require statements. This defect allows attackers to craft input that leads to arbitrary file inclusion from the server's file system. Exploiting an LFI vulnerability can result in unauthorized access to sensitive server files, potentially allowing attackers to view or execute unintended files or scripts. Such vulnerabilities are critical as they can pave the way for further exploitation, including remote code execution or data breaches. Consequently, addressing LFI vulnerabilities is essential in safeguarding server integrity and user data.

The technical details of this LFI vulnerability involve the inadequate validation of file paths within the Formality plugin. This flaw is particularly present in requests handled via crafted HTTP GET methods where parameters like 'file' are improperly sanitized. Specifically, the endpoint allowing downloadable exports is vulnerable when manipulated by unauthorized users who can access unintended files on the server. The demonstration of this vulnerability typically includes the ability to obtain contents of sensitive files, such as '/etc/passwd', proving unauthorized access to critical system information. Successful exploitation relies on crafting specific input or using enumeration techniques to identify exploitable parameters. Failure to correct this flaw can lead to disastrous security breaches, underscoring the need for proper patch management.

If exploited by malicious actors, this vulnerability could allow for arbitrary code execution, leading to complete server compromise. Attackers could leverage this flaw to access and download sensitive files, possibly revealing confidential and personal information stored on the server. This scenario poses significant risks of data leakage, intellectual property theft, and privacy invasion of users interacting with vulnerable websites. The operational disruption includes distributed denial-of-service (DDoS) attacks, modification or defacement of web content, and unauthorized takeover of site administration. Consequently, the repercussions extend beyond immediate data exposure to long-term reputational harm and legal liabilities for affected entities.

REFERENCES

Solution Advice
  • Update the WordPress Formality Plugin to a version beyond 1.5.9 to patch the Local File Inclusion vulnerability.
  • Regularly check for and apply security updates and patches for WordPress and its plugins.
  • Implement additional security measures such as Web Application Firewalls (WAF) to prevent unauthorized access to your server.
  • Conduct a comprehensive security audit to identify and rectify other potential vulnerabilities in your WordPress installation.
  • Educate staff and maintainers on safe coding practices to prevent future vulnerabilities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.