Missing AuthorizationWeakness · CWE-862

CVE-2026-3596

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-16

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The Riaxe Product Customizer plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.1.2. The plugin registers an unauthenticated AJAX action ('wp_ajax_nopriv_install-imprint') that maps to the ink_pd_add_option() function. This function reads 'option' and 'opt_value' from $_POST, then calls delete_option() followed by add_option() using these attacker-controlled values without any nonce verification, capability checks, or option name allowlist. This makes it possible for unauthenticated attackers to update arbitrary WordPress options, which can be leveraged for privilege escalation by enabling user registration and setting the default user role to administrator.

Technical summary

dbcve analysis · high confidence

The Riaxe Product Customizer WordPress plugin (versions up to 2.1.2) contains a critical privilege escalation vulnerability. The plugin registers an unauthenticated AJAX action 'wp_ajax_nopriv_install-imprint' that calls ink_pd_add_option() without any authentication, nonce verification, capability checks, or option name allowlisting. Attackers can manipulate arbitrary WordPress options by supplying 'option' and 'opt_value' POST parameters, enabling them to enable user registration and set the default role to administrator for unauthenticated account creation.

MitigationImmediately disable or remove the Riaxe Product Customizer plugin until patched. The fix requires adding authentication requirements, nonce verification, capability checks (current_user_can('manage_options')), and implementing an allowlist of permitted option names in the ink_pd_add_option() function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Riaxe Product Customizer plugin is installed

Navigate to WordPress admin dashboard > Plugins, or inspect the file /wp-content/plugins/riaxe-product-customizer/riaxe-product-customizer.php and check the version header comment

Affected if The plugin is installed and the version is 2.1.2 or lower (no version specified as fixed; treat any unpatched version as affected)
Confirm the vulnerable AJAX action is registered

Inspect the plugin's main PHP file for the line 'add_action("wp_ajax_nopriv_install-imprint", ...' or 'add_action("wp_ajax_install-imprint", ...' which registers the unauthenticated endpoint

Affected if The action 'wp_ajax_nopriv_install-imprint' is registered, allowing unauthenticated access to the ink_pd_add_option() function
Check if user registration is enabled

In WordPress admin, go to Settings > General > Membership (or inspect the 'users_can_register' option in wp_options table), or query: SELECT option_value FROM wp_options WHERE option_name = 'users_can_register'

Affected if users_can_register is set to '1' or 'true' (especially if you did not enable this yourself)
Check the default user role setting

In WordPress admin, go to Settings > General > New User Default Role (or inspect the 'default_role' option in wp_options table), or query: SELECT option_value FROM wp_options WHERE option_name = 'default_role'

Affected if default_role is set to 'administrator' and you did not intentionally set this
Audit for unauthorized administrator accounts

Query the wp_users and wp_usermeta tables: SELECT u.ID, u.user_login, u.user_registered, m.meta_key, m.meta_value FROM wp_users u JOIN wp_usermeta m ON u.ID = m.user_id WHERE m.meta_key = 'wp_capabilities' AND m.meta_value LIKE '%administrator%'; also check user_registered dates for recent accounts you did not create

Affected if There are administrator accounts you did not create, especially with recent user_registered timestamps

If the Riaxe Product Customizer plugin (version 2.1.2 or lower) is installed with the unauthenticated AJAX endpoint active, and either user registration is unexpectedly enabled, the default role is administrator, or unknown admin accounts exist, the environment is affected by CVE-2026-3596.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Immediately disable or remove the Riaxe Product Customizer plugin until patched. The fix requires adding authentication requirements, nonce verification, capability checks (current_user_can('manage_options')), and implementing an allowlist of permitted option names in the ink_pd_add_option() function.

Recommended fix Moderate confidence

Latest version of Riaxe Product Customizer plugin (version higher than 2.1.2)

1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
2. Locate the 'Riaxe Product Customizer' plugin
3. If an update is available, click 'Update Now' to install the latest version
4. After updating, verify the plugin version is newer than 2.1.2
5. Check WordPress Settings > General to ensure 'Membership' and 'Default Role' settings remain as intended (attackers may have modified these)
6. If compromised, disable new user registration, reset administrator passwords, and review user accounts for unauthorized additions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA3.0 h

16.0 hours of engineering $2,820

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-3596 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3596 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-3596?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 0.8%

Remediation

A high-priority fix

Have this fixed 16 hrs · High

Typical engagement from $2,820

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-3596 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References