CVE-2025-34434
BaseFortify
Publication date: 2025-12-17
Last updated on: 2025-12-19
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wwbn | avideo | to 20.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-306 | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows unauthenticated file upload and deletion without authentication or ownership validation, it could potentially lead to unauthorized access or manipulation of data, which may violate data protection and security requirements under such regulations. Still, no direct compliance implications are detailed in the provided texts. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-34434 is a critical vulnerability in AVideo versions prior to 20.0 with the ImageGallery plugin enabled. The plugin's endpoints that manage gallery images do not enforce authentication or validate ownership, allowing unauthenticated attackers to upload or delete images associated with any video. This means anyone can manipulate gallery images without logging in or having permission, due to missing authentication and authorization checks. [3, 2]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing unauthenticated attackers to upload malicious files or delete legitimate images in your video galleries. This can lead to unauthorized content manipulation, potential defacement, loss of important media, and could be exploited to execute further attacks such as remote code execution or distribution of malicious content. It compromises the integrity and availability of your media assets. [3, 1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
To detect this vulnerability, monitor for unauthorized HTTP requests to the ImageGallery plugin endpoints related to image upload and deletion, especially those that do not require authentication. You can use network traffic analysis tools like tcpdump or Wireshark to capture suspicious POST requests to endpoints such as 'list-images.upload.json.php' and 'list-images.delete.json.php'. For example, using tcpdump: `tcpdump -i any -A -s 0 'tcp port 80 or tcp port 443' | grep -E 'list-images\.upload\.json\.php|list-images\.delete\.json\.php'`. Additionally, check web server logs for unauthenticated POST requests to these endpoints. On the system, look for unexpected files uploaded to the video image directories or unexpected deletions. Commands like `find /path/to/avideo/videos -type f -mtime -1` can help identify recently modified files. Since the vulnerability allows unauthenticated file upload and deletion, any such activity without valid user sessions is suspicious. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading AVideo to version 20.0 or later, where the vulnerability is fixed by enforcing authentication and authorization checks on the ImageGallery plugin endpoints. Specifically, the fixes add user authentication verification (`User::isLogged()`) and authorization checks (`Video::canEdit()`) to ensure only authorized users can upload or delete images. If upgrading immediately is not possible, restrict access to the vulnerable endpoints by implementing network-level controls such as firewall rules or web application firewall (WAF) rules to block unauthenticated requests to the image upload and deletion endpoints. Additionally, review and sanitize any uploaded files and monitor logs for suspicious activity. Applying the official patches described in the commits that fix authorization enforcement and directory traversal issues is also recommended. [1, 2, 3]