The Mang Board plugin for WordPress is vulnerable to Local File Inclusion in all versions up to…

Why it is Amber

• CVSS 8.1 high
• Remotely exploitable without logging in

References

• https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.3/includes/class.board.php#L175
• https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.3/includes/class.store.php#L124
• https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.3/includes/functions/func.board.php#L360
• https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.3/mangboard.php#L181
• https://plugins.trac.wordpress.org/changeset/3738898/mangboard/trunk/includes/functions/func.board.php
• https://wordpress.org/plugins/mangboard/
• https://www.wordfence.com/threat-intel/vulnerabilities/id/cbf1cbe0-4740-4d76-a3f5-7d2e1a64d4ee?source=cve

Original description

The Mang Board plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.4.3 via the '<mode>_type (e.g. foo_type)' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. Exploitation is trivial via an unauthenticated POST to any page rendering a public [mb_board] shortcode, as no nonce or capability check is enforced on the shortcode render path; on servers with a standard PHP installation, pearcmd.php can be leveraged to write and then include an attacker-controlled payload file in a single request.