Skip to main content

CVE-2025-7401: CWE-798 Use of Hard-coded Credentials in aa-team Premium Age Verification / Restriction for WordPress

Critical
VulnerabilityCVE-2025-7401cvecve-2025-7401cwe-798
Published: Fri Jul 11 2025 (07/11/2025, 04:22:01 UTC)
Source: CVE Database V5
Vendor/Project: aa-team
Product: Premium Age Verification / Restriction for WordPress

Description

The Premium Age Verification / Restriction for WordPress plugin for WordPress is vulnerable to arbitrary file read and write due to the existence of an insufficiently protected remote support functionality in remote_tunnel.php in all versions up to, and including, 3.0.2. This makes it possible for unauthenticated attackers to read from or write to arbitrary files on the affected site's server which may make the exposure of sensitive information or remote code execution possible.

AI-Powered Analysis

AILast updated: 07/11/2025, 04:46:09 UTC

Technical Analysis

CVE-2025-7401 is a critical security vulnerability affecting the Premium Age Verification / Restriction plugin for WordPress developed by aa-team. This vulnerability arises from the presence of hard-coded credentials (CWE-798) within the plugin's remote support functionality implemented in the remote_tunnel.php file. The flaw exists in all versions up to and including 3.0.2. Due to insufficient protection of this remote support feature, unauthenticated attackers can exploit it to perform arbitrary file read and write operations on the web server hosting the affected WordPress site. This capability allows attackers to access sensitive information stored on the server, such as configuration files, user data, or credentials, and potentially write malicious files that could lead to remote code execution (RCE). The vulnerability has a CVSS 3.1 base score of 9.8, reflecting its critical severity with network attack vector, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the ease of exploitation and the severity of impact make this a significant threat to WordPress sites using this plugin. The root cause is the use of hard-coded credentials that cannot be changed or disabled by administrators, which is a recognized poor security practice. This vulnerability highlights the risks of embedding backdoor-like remote support mechanisms in web applications without robust authentication and access controls.

Potential Impact

For European organizations, this vulnerability poses a severe risk, especially for those relying on WordPress websites with the affected plugin installed. Exploitation could lead to unauthorized disclosure of sensitive personal data, intellectual property, or business-critical information, potentially violating GDPR and other data protection regulations. The ability to write arbitrary files and possibly execute code remotely could allow attackers to deploy web shells, pivot within internal networks, or disrupt website availability, causing reputational damage and operational downtime. Organizations in sectors such as e-commerce, media, healthcare, and government that use WordPress extensively are particularly vulnerable. The breach of confidentiality and integrity could lead to financial losses, regulatory fines, and erosion of customer trust. Given the plugin’s widespread use for age verification, sites targeting age-restricted content or services may also face legal compliance issues if exploited. The lack of required authentication and user interaction means attacks can be automated and launched at scale, increasing the threat surface for European entities.

Mitigation Recommendations

Immediate mitigation steps include uninstalling or disabling the Premium Age Verification / Restriction plugin until a secure patched version is released. Organizations should monitor official vendor channels for updates or patches addressing this vulnerability. In the interim, restricting access to the remote_tunnel.php file via web server configuration (e.g., IP whitelisting, .htaccess rules) can reduce exposure. Web application firewalls (WAFs) should be configured to detect and block suspicious requests targeting this endpoint. Conduct thorough audits of WordPress installations to identify the presence of this plugin and verify no unauthorized file modifications have occurred. Implement strict file system permissions to limit the web server’s ability to write to sensitive directories. Additionally, organizations should review their incident response plans to prepare for potential exploitation scenarios. Educating site administrators about the risks of using plugins with hard-coded credentials and encouraging the use of plugins from reputable sources with active maintenance is also critical to prevent similar issues.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-07-09T22:59:16.298Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6870938ba83201eaacabee32

Added to database: 7/11/2025, 4:31:07 AM

Last enriched: 7/11/2025, 4:46:09 AM

Last updated: 7/11/2025, 6:03:23 AM

Views: 4

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats