What is the severity of CVE-2022-36296?

CVE-2022-36296 is identified as a critical vulnerability due to its potential to allow unauthenticated users to create, update, or delete posts.

How do I fix CVE-2022-36296?

To fix CVE-2022-36296, update the ActiveDEMAND plugin to version 0.2.28 or later, which addresses the authentication issues.

What versions of the ActiveDEMAND plugin are affected by CVE-2022-36296?

CVE-2022-36296 affects versions of the ActiveDEMAND plugin up to and including 0.2.27.

What type of vulnerability is CVE-2022-36296?

CVE-2022-36296 is categorized as a Broken Authentication vulnerability.

Is CVE-2022-36296 specific to WordPress?

Yes, CVE-2022-36296 specifically affects the ActiveDEMAND plugin for WordPress.

Vulnerability/
CVE-2022-36296

medium

6.5

CWE

287

5/8/2022

20/2/2025

CVE-2022-36296: WordPress ActiveDEMAND plugin <= 0.2.27 - Broken Authentication vulnerability

First published: Fri Aug 05 2022(Updated: )

Broken Authentication vulnerability in JumpDEMAND Inc. ActiveDEMAND plugin <= 0.2.27 at WordPress allows unauthenticated post update/create/delete.

Credit: audit@patchstack.com audit@patchstack.com

Affected Software	Affected Version	How to fix
Activedemand	<=0.2.27

Remedy

Update to 0.2.28 or a higher version.

Never miss a vulnerability like this again

Reference Links

https://patchstack.com/database/vulnerability/activedemand/wordpress-activedemand-plugin-0-2-27-broken-authentication-vulnerability?_s_id=cve

Frequently Asked Questions

What is the severity of CVE-2022-36296?
CVE-2022-36296 is identified as a critical vulnerability due to its potential to allow unauthenticated users to create, update, or delete posts.
How do I fix CVE-2022-36296?
To fix CVE-2022-36296, update the ActiveDEMAND plugin to version 0.2.28 or later, which addresses the authentication issues.
What versions of the ActiveDEMAND plugin are affected by CVE-2022-36296?
CVE-2022-36296 affects versions of the ActiveDEMAND plugin up to and including 0.2.27.
What type of vulnerability is CVE-2022-36296?
CVE-2022-36296 is categorized as a Broken Authentication vulnerability.
Is CVE-2022-36296 specific to WordPress?
Yes, CVE-2022-36296 specifically affects the ActiveDEMAND plugin for WordPress.

agent/type
agent/remedy
agent/references
agent/severity
agent/title
agent/weakness
agent/description
agent/first-publish-date
agent/author
agent/softwarecombine
agent/event
agent/source
agent/tags
collector/mitre-cve
source/MITRE
agent/last-modified-date
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-api
source/NVD
agent/software-canonical-lookup
vendor/jumpdemand
canonical/activedemand
version/activedemand/0.2.27

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-36296?
CVE-2022-36296 is identified as a critical vulnerability due to its potential to allow unauthenticated users to create, update, or delete posts.
How do I fix CVE-2022-36296?
To fix CVE-2022-36296, update the ActiveDEMAND plugin to version 0.2.28 or later, which addresses the authentication issues.
What versions of the ActiveDEMAND plugin are affected by CVE-2022-36296?
CVE-2022-36296 affects versions of the ActiveDEMAND plugin up to and including 0.2.27.
What type of vulnerability is CVE-2022-36296?
CVE-2022-36296 is categorized as a Broken Authentication vulnerability.
Is CVE-2022-36296 specific to WordPress?
Yes, CVE-2022-36296 specifically affects the ActiveDEMAND plugin for WordPress.