Overview
CVE-2025-6991 is a significant security vulnerability discovered in the Kallyas theme for WordPress. This flaw allows authenticated attackers with Contributor-level access or higher to execute arbitrary PHP code on the server. It impacts all versions up to and including 4.21.0 of the Kallyas theme, potentially leading to system compromise or data leakage.
Vulnerability Summary
CVE ID: CVE-2025-6991
Severity: High (CVSS: 7.5)
Attack Vector: Local
Privileges Required: Contributor-level access
User Interaction: Required
Impact: Potential 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
Kallyas WordPress Theme | Up to and including 4.21.0
How the Exploit Works
The vulnerability resides in the ‘TH_LatestPosts4` widget of the Kallyas theme for WordPress. The flaw allows authenticated attackers, with Contributor-level access or higher, to include and execute arbitrary .php files on the server. This enables the execution of any PHP code present within the included files, which could bypass access controls, obtain sensitive data, or achieve code execution especially when .php file types can be uploaded and included.
Conceptual Example Code
Below is a conceptual example of how an attacker might exploit this vulnerability:
POST /wp-admin/admin-ajax.php?action=th_latest_posts4 HTTP/1.1
Host: target.example.com
Content-Type: application/x-www-form-urlencoded
file=../../../wp-config.php
In the example above, an attacker requests the WordPress configuration file (`wp-config.php`), which contains sensitive information such as database credentials. This request uses directory traversal (`../../../`) to navigate to the location of the `wp-config.php` file.
