CVE-2021-38607
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.6.1 allows XSS by remote authenticated users via a custom form input.
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 confidenceCrocoblock JetEngine before version 2.6.1 contains a stored Cross-Site Scripting (XSS) vulnerability in its custom form functionality. Authenticated users with access to create or edit forms can inject malicious JavaScript code through form input fields, which will execute when other users view the affected form submissions or the form in the frontend.
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< 2.6.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed JetEngine versionNavigate to WordPress admin > Plugins > Installed Plugins and locate JetEngine in the plugin list. The version number is displayed below the plugin name. Alternatively, check the version in the plugin's main PHP file header.Affected if The installed version is lower than 2.6.1
-
Verify custom forms module is activeGo to WordPress admin > JetEngine > Dashboard. Check if the Forms module is enabled or listed among active modules.Affected if The Forms module is enabled and in use
-
Check user roles with form accessNavigate to WordPress admin > JetEngine > Role Manager or WordPress Users section. Identify which user roles (Editor, Author, etc.) have permission to create or edit custom forms.Affected if Multiple untrusted or low-privilege user roles have form creation/edit capabilities
-
Inspect existing custom forms for XSS payloadsGo to WordPress admin > JetEngine > Forms > Post Forms. Review each custom form's field configurations. Look for field labels, names, or default values containing script tags, javascript:, or other HTML/JS code that appears malicious.Affected if Any form contains suspicious input patterns that could execute JavaScript
You are affected if JetEngine version is below 2.6.1 AND the custom forms module is active with accessible form creation capabilities.
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.6.1
Update JetEngine plugin to version 2.6.1 or later to apply the security patch. If immediate updating is not feasible, restrict form creation/edit permissions to only trusted administrative users and sanitize any existing custom form inputs.
JetEngine 2.6.1 or later
- Backup your WordPress database and files before making any changes
- Navigate to WordPress Admin > Plugins > JetEngine
- Check if an update to version 2.6.1 or newer is available
- If an update is available, click 'Update Now' to upgrade to the fixed version
- After updating, verify the plugin version shows 2.6.1 or later
- Test custom form functionality to confirm the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- 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-38607 — 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-38607 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