dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-4090

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.

NVD · unedited
The Inquiry Cart plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.4.2. This is due to missing nonce verification in the rd_ic_settings_page function when processing settings form submissions. This makes it possible for unauthenticated attackers to update the plugin's settings, including injecting malicious scripts that will be stored and executed in the admin area, via a forged request granted they can trick an administrator into performing an action such as clicking on a link.

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.

dbcve analysis · high confidence

The Inquiry Cart WordPress plugin fails to implement nonce verification in its settings handler function rd_ic_settings_page, allowing attackers to forge administrative requests. This CSRF vulnerability enables unauthenticated attackers to modify plugin settings and inject persistent malicious scripts that execute within the WordPress admin dashboard.

MitigationApply vendor patch or add nonce verification to the rd_ic_settings_page function by implementing wp_nonce_field() in the settings form and verifying with check_admin_referer() or wp_verify_nonce() before processing settings.

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

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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.

dbcve checks

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

  1. Confirm Inquiry Cart plugin is installed
    Navigate to WordPress admin > Plugins and verify 'Inquiry Cart' or 'rd-inquiry-cart' plugin is active. Alternatively, check /wp-content/plugins/ directory for inquiry-cart or similar folder name.
    Affected if The plugin is installed and active in WordPress.
  2. Locate the vulnerable settings function
    Access the plugin files via FTP or file manager. Find the file containing rd_ic_settings_page function, typically in the main plugin PHP file or a settings.php file within the plugin directory.
    Affected if The rd_ic_settings_page function exists in the plugin code.
  3. Inspect nonce verification in the settings handler
    Open the file containing rd_ic_settings_page and search for check_admin_referer() or wp_verify_nonce() calls before any settings processing logic.
    Affected if No nonce verification function is called before processing settings data - the plugin is vulnerable.
  4. Check the settings form for nonce field
    Find the HTML form that submits to rd_ic_settings_page. Inspect the form markup for wp_nonce_field() output or a hidden input with name containing '_nonce' or 'wpnonce'.
    Affected if The settings form does not contain a nonce field - the plugin is vulnerable.
  5. Verify if settings can be modified without authentication
    Test by submitting a settings update request from a non-authenticated browser (logged out) to the admin-ajax.php or settings page endpoint. Observe whether the request is processed without redirecting to login.
    Affected if Settings are processed without requiring admin authentication - confirms the CSRF vulnerability exists.

If the Inquiry Cart plugin is installed and the rd_ic_settings_page function lacks nonce verification (missing check_admin_referer or wp_verify_nonce) in its handler and the settings form lacks wp_nonce_field, the environment is affected by CVE-2026-4090.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch or add nonce verification to the rd_ic_settings_page function by implementing wp_nonce_field() in the settings form and verifying with check_admin_referer() or wp_verify_nonce() before processing settings.

Recommended fix Moderate confidence

Version 3.4.3 or later (verify latest available version on wordpress.org)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the Inquiry Cart plugin in the list
  3. 3. Check if an update is available by visiting the plugin page at wordpress.org/plugins/inquiry-cart/ or checking the Plugins > Add New > Upload section
  4. 4. If version 3.4.3 or higher is available, update the plugin to the latest version
  5. 5. After updating, verify that the plugin settings have not been tampered with by reviewing the plugin settings page
  6. 6. Consider implementing additional CSRF protections on the site using a security plugin or web application firewall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4090 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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