CVE-2026-5074
Deferred Deferred - Pending Action
SQL Injection in ARMember WordPress Plugin

Publication date: 2026-06-02

Last updated on: 2026-06-02

Assigner: Wordfence

Description
The ARMember Premium plugin for WordPress is vulnerable to SQL Injection via the 'sSortDir_0' parameter of the `get_private_content_data` AJAX action in all versions up to, and including, 7.3.1. This is due to insufficient sanitization of the user-supplied parameter which is concatenated directly into the ORDER BY clause of an SQL query without a whitelist check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Note: The vulnerability can only be exploited if the "User Private Content" addon is enabled, which is disabled by default..
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-02
Last Modified
2026-06-02
Generated
2026-06-03
AI Q&A
2026-06-02
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
armember premium_plugin to 7.3.1 (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 ARMember Premium plugin for WordPress has a SQL Injection vulnerability in the 'sSortDir_0' parameter of the get_private_content_data AJAX action in all versions up to and including 7.3.1.

This happens because the plugin does not properly sanitize the user-supplied parameter before including it directly in the ORDER BY clause of an SQL query without using a whitelist.

As a result, authenticated users with Subscriber-level access or higher can inject additional SQL queries into existing queries, potentially extracting sensitive information from the database.

Note that this vulnerability can only be exploited if the "User Private Content" addon is enabled, which is disabled by default.


How can this vulnerability impact me? :

This vulnerability allows attackers with at least Subscriber-level access to perform SQL Injection attacks, which can lead to unauthorized extraction of sensitive information from the database.

Because the attacker can append additional SQL queries, they might access data they should not be able to see, potentially compromising user privacy and data integrity.


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