CVE-2026-7472
Received Received - Intake
Time-Based Blind SQL Injection in Read More & Accordion WordPress Plugin

Publication date: 2026-05-20

Last updated on: 2026-05-20

Assigner: Wordfence

Description
The Read More & Accordion plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'orderby' parameter in all versions up to, and including, 3.5.7. This is due to the use of esc_sql() without surrounding the value in quotes in an ORDER BY clause inside the getAllDataByLimit() and getAccordionAllDataByLimit() functions in ReadMoreData.php. The user-supplied $_GET['orderby'] value is only processed through esc_attr() (an HTML-escaping function) before being passed to these database functions, where esc_sql() is applied but the value is directly concatenatedβ€”unquotedβ€”into the ORDER BY fragment of the SQL query before $wpdb->prepare() is called. Because esc_sql() only escapes quote characters and backslashes (which are irrelevant in an unquoted ORDER BY context), an attacker can inject arbitrary SQL expressions such as (SELECT SLEEP(5)) or conditional subqueries to perform time-based blind data extraction. This makes it possible for authenticated attackers with administrator-level access or above (or any role explicitly permitted access to the plugin's admin pages via the yrm-user-roles setting) to extract sensitive data from the database, including administrator credential hashes.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-20
Last Modified
2026-05-20
Generated
2026-05-20
AI Q&A
2026-05-20
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wp_read_more_accordion read_more_accordion to 3.5.7 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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
Can you explain this vulnerability to me?

The Read More & Accordion plugin for WordPress has a time-based blind SQL Injection vulnerability in the 'orderby' parameter in all versions up to 3.5.7. This happens because the plugin uses esc_sql() without quoting the value in an ORDER BY clause inside certain functions. The user input from $_GET['orderby'] is only HTML-escaped before being passed to the database functions, where it is escaped but concatenated unquoted into the SQL query. Since esc_sql() only escapes quotes and backslashes, which do not affect unquoted ORDER BY clauses, an attacker can inject SQL expressions like (SELECT SLEEP(5)) to perform time-based blind data extraction.

This vulnerability allows authenticated users with administrator-level access or roles permitted to access the plugin's admin pages to extract sensitive data from the database, including administrator credential hashes.


How can this vulnerability impact me? :

This vulnerability can allow an attacker with sufficient privileges (administrator or roles allowed access to the plugin's admin pages) to perform time-based blind SQL injection attacks. Through this, they can extract sensitive information from the database, such as administrator credential hashes.

The impact includes potential unauthorized access to sensitive data, which could lead to further compromise of the WordPress site or its users.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows authenticated attackers with sufficient privileges to extract sensitive data from the database, including administrator credential hashes. This exposure of sensitive data could potentially lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information.

However, the provided context does not explicitly discuss the impact on compliance with these standards or regulations.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart