JetengineWordPress extension · Crocoblock
CVE-2021-41844
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 · uneditedCrocoblock JetEngine before 2.9.1 does not properly validate and sanitize form data.
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 confidenceThe JetEngine plugin for WordPress fails to properly validate and sanitize form data submitted through its form builder component. This insufficient input handling in versions before 2.9.1 could allow attackers to inject malicious payloads via form submissions, potentially leading to cross-site scripting (XSS) or other injection-based attacks depending on how the form data is processed downstream.
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
JetengineWordPress extension
< 2.9.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify JetEngine plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'JetEngine' in the list of active pluginsAffected if JetEngine plugin is installed and active
-
Determine installed JetEngine versionIn WordPress admin, go to Plugins > Installed Plugins, find JetEngine, and note the version number displayedAffected if The version listed is lower than 2.9.1 (e.g., 2.9.0, 2.8.x, etc.)
-
Confirm JetEngine forms are in useNavigate to JetEngine > Forms in the WordPress dashboard and review if any forms have been createdAffected if Any JetEngine forms exist and are published or embedded on the site
-
Check if forms are publicly accessibleReview pages or posts where JetEngine forms are embedded and confirm they are accessible to unauthenticated visitorsAffected if JetEngine forms are rendered on public-facing pages accessible to site visitors
The site is affected if JetEngine is installed with a version lower than 2.9.1 AND JetEngine forms are created and accessible on the website.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.9.1
Update Crocoblock JetEngine to version 2.9.1 or later. Until the update is applied, consider disabling public-facing forms or implementing additional input filtering at the web application firewall (WAF) level.
JetEngine 2.9.1 or later
- Backup your WordPress site and database before making any changes
- Navigate to WordPress Admin > Plugins > Installed Plugins
- Find JetEngine in the plugin list
- Click 'Update now' if an update to version 2.9.1 or later is available, or manually upload the latest version from the WordPress repository or your Crocoblock account
- Verify the update completed successfully and the new version is active
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jetengine
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-41844 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-41844 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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