CVE-2026-2468
Received Received - Intake
SQL Injection in Quentn WP Plugin Allows Data Extraction

Publication date: 2026-03-21

Last updated on: 2026-03-21

Assigner: Wordfence

Description
The Quentn WP plugin for WordPress is vulnerable to SQL Injection via the 'qntn_wp_access' cookie in all versions up to, and including, 1.2.12. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query in the `get_user_access()` method. This makes it possible for unauthenticated attackers 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-21
Last Modified
2026-03-21
Generated
2026-05-07
AI Q&A
2026-03-21
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
quentn wp_plugin to 1.2.12 (inc)
quentn quentn_wp_plugin to 1.2.12 (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 Quentn WP plugin for WordPress has a vulnerability known as SQL Injection through the 'qntn_wp_access' cookie in all versions up to and including 1.2.12.

This happens because the plugin does not properly escape user-supplied input and does not sufficiently prepare the SQL query in the get_user_access() method.

As a result, an unauthenticated attacker can inject additional SQL commands into existing queries, potentially extracting sensitive information from the database.


How can this vulnerability impact me? :

This vulnerability allows unauthenticated attackers to perform SQL Injection attacks, which can lead to unauthorized access to sensitive data stored in the database.

Since the attacker can extract sensitive information without authentication, this can compromise the confidentiality of your data.

The CVSS score of 7.5 indicates a high severity impact on confidentiality, though it does not affect integrity or availability.


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