SQL Injection in Php-Nuke public_message (c_mid parameter)
A SQL injection vulnerability exists in the 'public message' capability (public_message) of Php-Nuke versions 6.x through 7.1.0. The vulnerability is due to insufficient sanitization of user-supplied input in the c_mid parameter, allowing attackers to inject arbitrary SQL queries. This can be exploited to retrieve sensitive information, such as the administrator password, from the database.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote attackers to execute arbitrary SQL commands against the Php-Nuke database, leading to disclosure of sensitive information, including administrator credentials, and potentially full compromise of the application and underlying server.
If you can’t patch tonight, do this now.
Restrict access to the public_message functionality where possible. Employ web application firewalls (WAFs) with rules to detect and block SQL injection attempts. Ensure that database accounts used by the application have the least privileges necessary.
Patch, then assume compromise.
Upgrade to a version of Php-Nuke later than 7.1.0 where this vulnerability is patched. Alternatively, apply vendor-supplied patches or manually sanitize and validate all user input, especially the c_mid parameter, to prevent SQL injection.
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.