The AGE-GATE plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and…

Why it is Amber

• CVSS 9.8 critical
• Remotely exploitable without logging in

References

• https://plugins.trac.wordpress.org/browser/wp-site-age-gate/trunk/admin.php
• https://plugins.trac.wordpress.org/browser/wp-site-age-gate/trunk/agegate.php#L161
• https://plugins.trac.wordpress.org/browser/wp-site-age-gate/trunk/main.php#L213
• https://plugins.trac.wordpress.org/browser/wp-site-age-gate/trunk/main.php#L279
• https://plugins.trac.wordpress.org/browser/wp-site-age-gate/trunk/main.php#L291
• https://plugins.trac.wordpress.org/browser/wp-site-age-gate/trunk/main.php#L325
• https://plugins.trac.wordpress.org/browser/wp-site-age-gate/trunk/nonwp.php#L20
• https://www.wordfence.com/threat-intel/vulnerabilities/id/05db28b4-a3de-402d-bc5b-06d5347d6724?source=cve

Original description

The AGE-GATE plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.0 via the 'width (and height)' parameter parameter. This is due to missing authentication, capability checks, and nonce verification on the standalone admin.php endpoint, combined with unsanitized injection of POST parameters directly into generated PHP source written to an included file. This makes it possible for unauthenticated attackers to execute code on the server. This is possible because admin.php does not load WordPress and carries no ABSPATH guard, making it a fully unauthenticated entry point regardless of the decorative capability arguments registered via the plugin's simulated menu API.