CVE-2021-20736
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 · uneditedNoSQL injection vulnerability in GROWI versions prior to v4.2.20 allows a remote attacker to obtain and/or alter the information stored in the database via unspecified vectors.
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 confidenceGROWI v4.2.20之前存在NoSQL注入漏洞，远程攻击者可通过在用户输入中注入MongoDB查询操作来获取或篡改数据库中的数据。由于GROWI使用MongoDB作为后端存储，恶意查询可绕过应用层验证直接操作数据库。
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< 4.2.20CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 GROWI versionCheck the version file or package.json in the GROWI installation directory. If using Docker, run 'docker images' to see the image tag. Alternatively, access the GROWI admin panel and look for version information in the system settings.Affected if The installed version is below 4.2.20
-
Confirm MongoDB backend is in useCheck the GROWI configuration file (e.g., config.yaml, .env, or mongolab.yml) for the MONGO_URI or MONGODB_URI setting. Verify that GROWI is configured to connect to a MongoDB database.Affected if MongoDB is configured as the backend database (this is the default and required for this vulnerability)
-
Identify accessible user input endpointsReview GROWI's publicly accessible pages that accept user input, such as the login form, registration form, search functionality, or page creation/editing interfaces. These are potential injection points.Affected if User-facing input fields exist that process data against the MongoDB backend without sanitization
You are affected if GROWI version is below 4.2.20 AND MongoDB is used as the backend database, as the vulnerability allows injection of malicious MongoDB queries through user input fields.
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 · scoped4.2.20
立即将GROWI升级至v4.2.20或更高版本以修复此NoSQL注入漏洞。升级前应备份数据库，并在测试环境中验证升级不会影响现有功能。
v4.2.20 or later
- Backup your GROWI data and database before starting the upgrade process
- Stop the currently running GROWI instance
- Update GROWI to version 4.2.20 or later. If using Docker, pull the new image: docker pull weseek/growi:4.2.20 or higher
- Review the release notes for v4.2.20 to check for any required configuration changes
- Restart GROWI with the new version
- Verify the installation by logging in and checking that the application functions normally
- Monitor logs for any errors or unusual activity following the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-20736 — 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-20736 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