S4E just found a high top 10 tcp port service scan
critical·Product Based Web Vulnerabilities·Updated Aug 3, 2026

CVE-2025-2505 Scanner

CVE-2025-2505 Scanner - Local File Inclusion (LFI) vulnerability in WordPress Age Gate

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
0
Times Used
by S4E users
0
Assets Scanned
domains & IPs
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2025-2505
9.8
CVSScritical
Exploitable remotely over the internet · no authentication required.

The Age Gate plugin for WordPress is vulnerable to Local PHP File Inclusion in all versions up to, and including, 3.5.3 via the 'lang' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary PHP files on the server, allowing the execution of code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
Age Gateby philsbury
0
Updated Aug 19, 2026View on NVD →
Detail

The WordPress Age Gate plugin is a tool used by website administrators to restrict access to content based on the age of the viewer, ensuring compliance with legal and regulatory standards. It is widely utilized in industries such as alcohol, tobacco, and gaming, where age verification is critical. The plugin provides a simple interface for setting age restrictions and can be configured to display customizable age verification screens. It integrates seamlessly with the WordPress platform, enhancing functionality without requiring advanced technical knowledge. Users of the plugin find it useful for protecting sensitive content from underage viewers. As it integrates with WordPress, which is a widely used content management system, it has a broad user base.

The vulnerability in question is a Local File Inclusion (LFI) flaw in the WordPress Age Gate plugin that affects versions up to 3.5.3. LFI allows attackers to manipulate file paths and include files from the local file system on the web server. The flaw is introduced through the 'lang' parameter, making it possible for unauthenticated users to include and execute PHP files. This can lead to significant security risks as it may compromise the entire server. The vulnerability is classified as critical, with an associated CVSS score of 9.8, indicating the severe impact it can potentially have on unpatched systems. This issue is particularly concerning as it enables remote code execution without authentication.

The Local File Inclusion vulnerability exploits the 'lang' parameter within the Age Gate plugin's API endpoint by allowing unauthorized users to include files stored on the server. By crafting a malicious request, attackers can access sensitive files such as 'wp-config.php', which contain critical configuration details of the WordPress installation. The attack does not require any authentication, significantly increasing its risk level. The attack vector is web-based, exploiting the improper handling of input within the specific endpoint used for age verification checks. Successful exploitation relies on navigating the server's directory structure via path traversal techniques.

If exploited, this vulnerability can lead to a complete server compromise. Attackers might execute arbitrary PHP code, leading to the theft of sensitive information such as database credentials. Moreover, it could allow the attacker to upload malware or modify existing files to introduce persistent backdoors. The server's integrity would be impacted, potentially resulting in unauthorized administrative access. Also, the attacker might leverage the compromised server to launch further attacks on connected networks or systems. Overall, the consequences of an exploited LFI in Age Gate can be severe and far-reaching.

REFERENCES

Solution Advice
Remediation:
  • Update the WordPress Age Gate plugin to version 3.5.4 or later to patch the vulnerability.
  • Configure web server permissions to restrict read access to sensitive files.
  • Implement input validation and sanitization for all user inputs to prevent path traversal exploits.
  • Regularly monitor and audit logs for unauthorized file inclusion attempts and respond promptly to suspicious activities.
  • Consider deploying a Web Application Firewall (WAF) to mitigate similar 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.