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-3103: Arbitrary File Read Vulnerability in CLEVER – HTML5 Radio Player With History – Shoutcast and Icecast – Elementor Widget Addon Plugin for WordPress

Ameeba Chat Store screens
Download Ameeba Chat

Overview

This report covers an arbitrary file read vulnerability in the CLEVER – HTML5 Radio Player With History – Shoutcast and Icecast – Elementor Widget Addon plugin for WordPress. This vulnerability allows unauthenticated attackers to read arbitrary files on the server of an affected site, which may contain sensitive information like database credentials. It’s a serious issue that can expose critical data and potentially compromise the entire system.

Vulnerability Summary

CVE ID: CVE-2025-3103
Severity: High (7.5 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise or data leakage due to unauthorized access to sensitive files

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

CLEVER – HTML5 Radio Player With History – Shoutcast and Icecast – Elementor Widget Addon plugin for WordPress | Up to and including 2.4

How the Exploit Works

The vulnerability is due to insufficient file path validation in the ‘history.php’ file. An attacker can send a specially crafted request to the server hosting the vulnerable plugin. The server, failing to properly validate the requested file path, will return the content of any file specified by the attacker.

Conceptual Example Code

Below is a conceptual example of how this vulnerability might be exploited using an HTTP GET request. In this example, the attacker attempts to read the ‘wp-config.php’ file, which typically contains sensitive information such as database credentials.

GET /wp-content/plugins/clever-html5-radio-player/history.php?file=../../../wp-config.php HTTP/1.1
Host: target.example.com

Mitigation Guidance

To mitigate this vulnerability, apply the vendor patch as soon as possible. If a patch cannot be immediately applied, use a Web Application Firewall (WAF) or Intrusion Detection System (IDS) as a temporary mitigation. These systems can be configured to block or alert on attempts to exploit this vulnerability.

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