Calderawp License ManagerWordPress extension · Claderaform

CVE-2021-36914

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-12
Fix available
A fix is available. Upgrade to after 1.2.11 or later.
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
Cross-Site Request Forgery (CSRF) vulnerability leading to Reflected Cross-Site Scripting (XSS) in CalderaWP License Manager (WordPress plugin) <= 1.2.11.

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

CSRF vulnerability in CalderaWP License Manager plugin allows attackers to trick authenticated administrators into executing malicious requests. Since the plugin lacks proper CSRF token validation, attackers can craft malicious links that, when clicked by a logged-in admin, cause the browser to execute arbitrary JavaScript (Reflected XSS), potentially stealing session cookies or performing unauthorized actions.

MitigationUpdate CalderaWP License Manager to the latest version (if available) or remove/disable the plugin until a patch is released. Enforce CSRF tokens on all form submissions and AJAX actions.

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
Calderawp License ManagerWordPress extension
Affected:<= 1.2.11

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. Verify CalderaWP License Manager is installed
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'CalderaWP License Manager' or 'Calderaforms License Manager'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'caldera-wp-license-manager' or similar license manager naming.
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin > Plugins, find the CalderaWP License Manager entry and look for the version number displayed beneath the plugin name. Alternatively, check the main plugin PHP file header for 'Version:' comment or examine the plugin's readme.txt for the stable tag.
    Affected if Version is 1.2.11 or lower
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify the CalderaWP License Manager shows as 'Active' (not deactivated or deleted).
    Affected if Plugin is currently activated on the WordPress site
  4. Inspect form submissions for CSRF protection
    Examine the plugin's PHP source files (particularly form handlers and AJAX endpoints) for presence of wp_nonce_field, wp_verify_nonce, or nonce verification. Search for 'nonce' in the license-manager related PHP files.
    Affected if No CSRF nonce tokens are implemented in form submissions or AJAX actions within the plugin

You are affected if CalderaWP License Manager version 1.2.11 or lower is installed and active, with no CSRF token validation found in the plugin's code.

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.

From vendor data
Upgrade available Upgrade to a release after 1.2.11
Interim mitigation

Update CalderaWP License Manager to the latest version (if available) or remove/disable the plugin until a patch is released. Enforce CSRF tokens on all form submissions and AJAX actions.

Fix this in Calderawp License Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2021-36914 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