CVE-2026-2412
Received Received - Intake
SQL Injection in Quiz and Survey Master Plugin Allows Data Exposure

Publication date: 2026-03-23

Last updated on: 2026-03-23

Assigner: Wordfence

Description
The Quiz and Survey Master (QSM) plugin for WordPress is vulnerable to SQL Injection via the 'merged_question' parameter in all versions up to, and including, 10.3.5. This is due to insufficient sanitization of user-supplied input before being used in a SQL query. The sanitize_text_field() function applied to the merged_question parameter does not prevent SQL metacharacters like ), OR, AND, and # from being included in the value, which is then directly concatenated into a SQL IN() clause without using $wpdb->prepare() or casting values to integers. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-23
Last Modified
2026-03-23
Generated
2026-05-07
AI Q&A
2026-03-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
quiz_and_survey_master qsm to 10.3.5 (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 Quiz and Survey Master (QSM) plugin for WordPress has a SQL Injection vulnerability in the 'merged_question' parameter in all versions up to and including 10.3.5. This happens because the plugin does not properly sanitize user input before using it in a SQL query. Specifically, the sanitize_text_field() function does not block SQL metacharacters such as ), OR, AND, and #. These characters are then directly concatenated into a SQL IN() clause without proper preparation or casting, allowing attackers with Contributor-level access or higher to inject additional SQL queries.

This vulnerability enables attackers to manipulate SQL queries to extract sensitive information from the database.


How can this vulnerability impact me? :

This vulnerability can allow authenticated users with Contributor-level access or above to perform unauthorized SQL queries on the database. As a result, attackers may extract sensitive information stored in the database, potentially leading to data breaches or exposure of confidential data.


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

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


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