CVE-2024-8268

Improper Control of Generation of Code ('Code Injection') (CWE-94)

Published: Sep 10, 2024 / Updated: 2mo ago

010
CVSS 8.8EPSS 0.06%High
CVE info copied to clipboard

Summary

The Frontend Dashboard plugin for WordPress is vulnerable to unauthorized code execution due to insufficient filtering on callable methods/functions via the ajax_request() function in all versions up to, and including, 2.2.4. This vulnerability allows authenticated attackers with subscriber-level access and above to call arbitrary functions, which can be leveraged for privilege escalation by changing user's passwords.

Impact

This vulnerability has a high severity impact. Attackers with low-level authenticated access (subscriber or above) can execute unauthorized code, potentially leading to privilege escalation. They could change user passwords, including those of administrators, effectively taking control of the WordPress site. This could result in unauthorized access to sensitive information, manipulation of website content, and potential complete compromise of the affected WordPress installation.

Exploitation

There is no evidence that a public proof-of-concept exists. There is no evidence of proof of exploitation at the moment.

Patch

A patch is available. The vulnerability affects all versions of the Frontend Dashboard plugin for WordPress up to and including version 2.2.4. A fix has been implemented in version 2.2.5, as indicated by the patch details provided.

Mitigation

1. Update the Frontend Dashboard plugin to version 2.2.5 or later as soon as possible. 2. If immediate updating is not possible, disable or remove the Frontend Dashboard plugin from all WordPress installations until the update can be applied. 3. Conduct a thorough review of user accounts and their privileges, especially focusing on subscriber-level accounts that might have been compromised. 4. Implement strong password policies and enable two-factor authentication for all user accounts, especially administrator accounts. 5. Monitor WordPress installations for any suspicious activities, particularly those related to user privilege changes or unexpected password resets. 6. Consider implementing a Web Application Firewall (WAF) to help detect and block potential exploitation attempts. 7. Regularly backup your WordPress installations and keep them up-to-date, including all plugins and themes. 8. After updating, test the plugin functionality in a staging environment before deploying to production.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Timeline

First Article

Feedly found the first article mentioning CVE-2024-8268. See article

Sep 10, 2024 at 2:31 AM / CVE
CVSS Estimate

Feedly estimated the CVSS score as HIGH

Sep 10, 2024 at 2:32 AM
CVE Assignment

NVD published the first details for CVE-2024-8268

Sep 10, 2024 at 3:15 AM
CVSS

A CVSS base score of 8.8 has been assigned.

Sep 10, 2024 at 3:15 AM / nvd
EPSS

EPSS Score was set to: 0.06% (Percentile: 23.6%)

Sep 10, 2024 at 9:57 AM
Detection in Vulnerability Scanners

Detection for the vulnerability has been added to Qualys (152217)

Sep 20, 2024 at 7:53 AM
Static CVE Timeline Graph

Affected Systems

Buffercode/frontend_dashboard
+null more

Patches

plugins.trac.wordpress.org
+null more

Attack Patterns

CAPEC-242: Code Injection
+null more

News

Web Application Detections Published in September 2024
In September, Qualys released QIDs targeting vulnerabilities in several widely-used software products, including WordPress, Tiki Wiki CMS, Apache HTTP Server, XWiki, Apache OFBiz, Lunary-ai, GitLab, Adobe ColdFusion, Moodle CMS, Zimbra, JBoss EAP, Kibana, Drupal, Ivanti Endpoint Manager (EPM), Apache Tomcat, Joomla!, Nginx, Open Secure Sockets Layer (OpenSSL). Customers can get more details about the following QIDs in our knowledge base. Customers should review their reports for these detections. If any of the following are reported against their applications scanned, customers should follow the steps mentioned in the solution to ensure their systems are protected against the identified vulnerabilities. QID Title 152148 WordPress WPML Plugin: Remote Code Execution Vulnerability (CVE-2024-6386) 152150 WordPress Bit Form Plugin: SQL Injection Vulnerability (CVE-2024-7702) 152151 WordPress Bit Form Plugin: Arbitrary File Read And Delete Vulnerability (CVE-2024-7777) 152157 WordPress LiquidPoll Plugin: Stored Cross-Site Scripting Vulnerability (CVE-2024-7134) 152158 WordPress GEO my WP Plugin: Local File Inclusion Vulnerability (CVE-2024-6330) 152159 WordPress AI Engine Plugin:
Wordfence Intelligence Weekly WordPress Vulnerability Report (September 9, 2024 to September 15, 2024)
The team rolled out enhanced protection via firewall rules for the following vulnerabilities in real-time to our Premium, Care, and Response customers last week: Please note that if you run the Wordfence plugin on your WordPress site, with the scanner enabled, you should’ve already been notified if your site was affected by any of these vulnerabilities.
Security Bulletin 11 Sep 2024 - Cyber Security Agency of Singapore
The MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress ... MindsDB is a platform for building artificial ...
High - CVE-2024-8268 - The Frontend Dashboard plugin for WordPress is...
The Frontend Dashboard plugin for WordPress is vulnerable to unauthorized code execution due to insufficient filtering on callable methods/functions via the ajax_request() function in all versions...
CVE-2024-8268
Gravedad 3.1 (CVSS 3.1 Base Score) Gravedad 3.1 Txt Gravedad 3.1 (CVSS 3.1 Base Score)
See 7 more articles and social media posts

CVSS V3.1

Attack Vector:Network
Attack Complexity:Low
Privileges Required:Low
User Interaction:None
Scope:Unchanged
Confidentiality:High
Integrity:High
Availability Impact:High

Categories

Be the first to know about critical vulnerabilities

Collect, analyze, and share vulnerability reports faster using AI