CVE-2026-3596
Privilege Escalation via Unauthenticated Option Update in Riaxe Plugin
Publication date: 2026-04-16
Last updated on: 2026-04-16
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| riaxe | product_customizer | to 2.1.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthenticated attackers to escalate privileges by modifying arbitrary WordPress options, including enabling user registration and setting the default user role to administrator.
Such unauthorized privilege escalation can lead to unauthorized access to sensitive data or administrative functions, which may result in violations of common standards and regulations like GDPR and HIPAA that require strict access controls and protection of personal and health information.
Therefore, exploitation of this vulnerability could compromise compliance with these regulations by enabling attackers to bypass security controls and access or manipulate protected data.
Can you explain this vulnerability to me?
The Riaxe Product Customizer plugin for WordPress has a vulnerability in all versions up to and including 2.1.2. It registers an unauthenticated AJAX action called 'wp_ajax_nopriv_install-imprint' that triggers the ink_pd_add_option() function. This function reads 'option' and 'opt_value' from POST requests and then deletes and adds WordPress options based on these attacker-controlled values without any security checks such as nonce verification, capability checks, or an option name allowlist.
Because of this lack of verification, unauthenticated attackers can update arbitrary WordPress options. This can be exploited to escalate privileges by enabling user registration and setting the default user role to administrator.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to modify WordPress options arbitrarily, which can lead to privilege escalation.
- Attackers can enable user registration on the site.
- They can set the default user role to administrator, giving themselves full control over the WordPress site.
As a result, attackers can gain administrative access without authentication, potentially compromising the entire website.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking for the presence of the vulnerable Riaxe Product Customizer plugin version 2.1.2 or earlier on your WordPress installation.
Additionally, monitoring for unauthenticated POST requests to the AJAX action 'wp_ajax_nopriv_install-imprint' can help identify exploitation attempts.
Since the vulnerability allows arbitrary modification of WordPress options via POST parameters 'option' and 'opt_value', you can look for suspicious HTTP POST requests targeting the endpoint /wp-admin/admin-ajax.php with the action parameter set to 'install-imprint'.
Example command to detect such requests in web server logs (assuming Apache logs):
- grep 'admin-ajax.php' /var/log/apache2/access.log | grep 'action=install-imprint'
You can also use network monitoring tools like tcpdump or Wireshark to filter HTTP POST requests containing 'action=install-imprint'.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Riaxe Product Customizer plugin to a version later than 2.1.2 where this vulnerability is fixed.
If an update is not immediately available, temporarily disable or remove the plugin to prevent exploitation.
Additionally, restrict access to the AJAX action 'wp_ajax_nopriv_install-imprint' by implementing server-level rules or WordPress hooks to block unauthenticated requests.
Review and harden WordPress option settings, especially those related to user registration and default user roles, to prevent privilege escalation.