Overview
CVE-2025-7664 is a serious security vulnerability that affects the AL Pack plugin for WordPress. The flaw, which allows unauthenticated users to gain unauthorized access and activate premium features, could potentially lead to system compromise or data leakage. The widespread use of WordPress makes this vulnerability particularly problematic, warranting immediate attention and action.
Vulnerability Summary
CVE ID: CVE-2025-7664
Severity: High – 7.5 (CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
AL Pack for WordPress | All versions up to, and including, 1.0.2
How the Exploit Works
The vulnerability stems from a missing capability check on the check_activate_permission() permission callback for the /wp-json/presslearn/v1/activate REST API endpoint in the AL Pack plugin for WordPress. The callback reads the client-supplied Origin header and, after parsing, allows the request if it matches one of the trusted domains, without ever verifying user authentication, capabilities, or nonce tokens. As a result, unauthenticated attackers can activate premium features by simply spoofing the Origin header.
Conceptual Example Code
Here’s a conceptual HTTP request that could potentially exploit this vulnerability:
POST /wp-json/presslearn/v1/activate HTTP/1.1
Host: target.example.com
Origin: trusted.example.com
Content-Type: application/json
{ "premium_features": "activate" }
In this example, the attacker spoofs the Origin header to match a trusted domain, thereby bypassing the permission check and activating the premium features.
Recommended Mitigation Steps
To mitigate this vulnerability, it’s recommended to apply the vendor patch. In its absence, using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) could serve as a temporary solution. Regularly updating and patching software is an essential part of maintaining an effective security posture.
