dbcve.org
ActivedemandWordPress extension · Jumpdemand

CVE-2022-36296

MEDIUM · 5.3 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to after 0.2.27 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Broken Authentication vulnerability in JumpDEMAND Inc. ActiveDEMAND plugin <= 0.2.27 at WordPress allows unauthenticated post update/create/delete.

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

Broken authentication in the ActiveDEMAND WordPress plugin (versions 0.2.27 and below) allows unauthenticated attackers to bypass authentication checks and create, update, or delete arbitrary posts on the affected WordPress site.

MitigationUpdate the ActiveDEMAND plugin to a version newer than 0.2.27. If no patched version is available, disable and remove the plugin, or implement an alternative solution.

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
ActivedemandWordPress extension
Affected:<= 0.2.27

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 ActiveDEMAND plugin installation status
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins. Search for 'ActiveDEMAND' or 'Jumpdemand Activatedemand' in the plugin list.
    Affected if The plugin is not found in the installed plugins list, then the environment is NOT affected by this CVE.
  2. Check installed ActiveDEMAND version
    In the Plugins list, locate the ActiveDEMAND plugin entry. The version number is displayed beneath the plugin name. Alternatively, access via Plugins > Installed Plugins > ActiveDEMAND > View Details.
    Affected if If the displayed version number is 0.2.27 or lower (for example, 0.2.26, 0.2.25, etc.), then the environment IS affected by this CVE.
  3. Confirm plugin is active
    In the Plugins list, check if ActiveDEMAND shows a 'Active' status or a link to 'Deactivate'. The plugin must be both installed AND active for the vulnerability to be exploitable.
    Affected if If the plugin is installed with version 0.2.27 or below AND is currently active, then the environment IS vulnerable to unauthenticated post manipulation.
  4. Audit recent posts for unauthorized changes
    Go to Posts > All Posts in the WordPress admin. Review the list for any posts created, modified, or deleted that you do not recognize. Check the 'Author' column and 'Date' column for anomalies.
    Affected if If unexpected posts appear that were not created by legitimate administrators, this may indicate the vulnerability has been exploited.

Your environment is affected if the ActiveDEMAND WordPress plugin is installed, active, and running version 0.2.27 or lower.

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 a release after 0.2.27
Interim mitigation

Update the ActiveDEMAND plugin to a version newer than 0.2.27. If no patched version is available, disable and remove the plugin, or implement an alternative solution.

Recommended fix Moderate confidence

Upgrade ActiveDEMAND plugin to version 0.2.28 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins
  3. Locate the ActiveDEMAND plugin
  4. Check the current installed version to confirm it is <= 0.2.27
  5. If an update is available, click 'Update Now' to upgrade to the latest fixed version
  6. After updating, verify the new version is installed (version > 0.2.27)
  7. Test that unauthenticated users can no longer create, update, or delete posts

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

Fix this in Activedemand Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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