dbcve.org
Optimonk\Application · Optimonk

CVE-2023-37891

HIGH · 8.8 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to 2.0.5 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in OptiMonk OptiMonk: Popups, Personalization & A/B Testing plugin <= 2.0.4 versions.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the OptiMonk WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings or creating/changing popups) by forcing their browser to send malicious requests.

MitigationUpdate OptiMonk plugin to a version newer than 2.0.4; alternatively, implement anti-CSRF tokens (nonce validation) on all state-changing plugin actions and forms.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Optimonk\Application
Affected:< 2.0.5

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check OptiMonk plugin version
    In WordPress admin, go to Plugins > Installed Plugins > OptiMonk and note the version number displayed; alternatively, open /wp-content/plugins/optimonk/optimonk.php and look for the 'Version:' header in the plugin comment block
    Affected if Version is lower than 2.0.5
  2. Inspect plugin admin pages for nonce validation
    Access the OptiMonk plugin settings page (usually under Settings > OptiMonk or a dedicated OptiMonk admin menu), then view the page source or examine the plugin PHP files in /wp-content/plugins/optimonk/ to see if form submissions include a '_wpnonce' or 'nonce' field
    Affected if Forms and state-changing actions lack nonce token fields or do not verify nonces before processing requests
  3. Check AJAX action handlers for nonce verification
    Examine the plugin's AJAX handlers (typically in optimonk.php or separate files in the /includes/ folder) and look for calls to 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' before processing requests
    Affected if AJAX actions that modify settings, create popups, or change plugin configuration do not verify nonce tokens
  4. Review plugin action hooks for CSRF protection
    Search the plugin source code for 'add_action' hooks handling form submissions (e.g., 'admin_post_', 'init' handlers for state changes) and verify each calls a nonce verification function before executing the action
    Affected if Any admin action hooks that modify plugin state or settings skip nonce verification

Environment is affected if the OptiMonk plugin version is below 2.0.5 AND the plugin code lacks nonce validation on forms, AJAX handlers, or admin action hooks that modify settings or create/modify popups.

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
Upgrade available Upgrade to 2.0.5 or later
Fixed in 2.0.5
Interim mitigation

Update OptiMonk plugin to a version newer than 2.0.4; alternatively, implement anti-CSRF tokens (nonce validation) on all state-changing plugin actions and forms.

Recommended fix High confidence

OptiMonk plugin version 2.0.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the OptiMonk: Popups, Personalization & A/B Testing plugin
  4. Check the current version to confirm it is 2.0.4 or lower
  5. Click 'Update now' if an update to version 2.0.5 or newer is available
  6. Alternatively, navigate to Dashboard > Updates and apply available updates
  7. After updating, verify the plugin version shows 2.0.5 or higher

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

Fix this in Optimonk\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37891 — 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-2023-37891 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