CVE-2021-47915
Remote SQL Injection in PHP Melody 3.0 Video Edit Module
Publication date: 2026-02-01
Last updated on: 2026-02-11
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpsugar | php_melody | 3.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
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 specify how the CVE-2021-47915 vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2021-47915 is a remote SQL injection vulnerability in PHP Melody version 3.0, specifically in the video edit module. It occurs because the 'vid' parameter is not properly validated, allowing authenticated attackers with moderator or admin privileges to inject malicious SQL commands. This enables them to execute arbitrary database queries, potentially compromising the web application and the underlying database management system. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Applying the vendor's patch released on September 22, 2021. 2) Using prepared statements for all database queries involving the 'vid' parameter. 3) Restricting input parameters to disallow special characters that could be used in SQL injection. 4) Properly escaping and encoding all inputs to prevent execution of malicious payloads. 5) Optionally, integrating a web application firewall or filtering mechanisms to block SQL injection attacks. [2]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to significant compromise of the web application and the database management system. Attackers can execute arbitrary SQL queries, which may result in unauthorized data access, data manipulation, or extraction of sensitive information. This can compromise the confidentiality and integrity of the system, potentially leading to full control over the database and web server. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be performed by testing the 'vid' parameter in the edit-video.php file for SQL injection vulnerabilities. Two proof-of-concept techniques include: 1) Using a UNION-based SQL injection payload to extract data, and 2) Using a time-based blind SQL injection payload with the SLEEP function to confirm the vulnerability. For example, sending crafted GET requests with SQL injection payloads in the 'vid' parameter to the admin control panel interface can help detect the issue. Specific commands would involve curl or similar tools to send these requests, such as: curl "http://target/edit-video.php?vid=1' UNION SELECT ... -- " or curl "http://target/edit-video.php?vid=1' AND SLEEP(5)-- ". These tests require authenticated access with moderator or admin privileges. [2]