CVE-2021-3370
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 · uneditedDouPHP v1.6 was discovered to contain a cross-site scripting (XSS) vulnerability via /admin/cloud.php.
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 confidenceDouPHP v1.6 contains a cross-site scripting (XSS) vulnerability in the admin panel at /admin/cloud.php. An attacker can inject malicious JavaScript code through this endpoint, which executes in the browsers of other admin users.
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= 1.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 DouPHP installation versionCheck the version file or admin footer for the installed DouPHP version number. Common locations include a version.php file, CHANGELOG file, or the admin panel footer.Affected if The installed version is exactly 1.6 (Douco Douphp version 1.6)
-
Locate the cloud.php admin scriptVerify the presence of the /admin/cloud.php file in the web root directory. Check if the file exists on the server filesystem.Affected if The file /admin/cloud.php exists in the DouPHP installation
-
Confirm admin panel accessibilityDetermine if the admin panel is accessible by attempting to access the /admin/ login page or by checking web server configuration for admin route exposure.Affected if The admin panel is accessible without additional access controls beyond standard authentication
-
Identify the vulnerable parameterReview the source code of /admin/cloud.php to locate user-supplied input parameters (typically GET or POST requests) that are reflected in the page output without sanitization.Affected if User-supplied parameters in cloud.php are processed and displayed without input validation or output encoding
-
Check for existing XSS filtersInspect the application code for any existing input validation, sanitization, or output encoding functions applied to parameters in /admin/cloud.php.Affected if No XSS filtering or output encoding is implemented for the affected parameters in cloud.php
A user is affected if they are running Douco Douphp version 1.6 with the /admin/cloud.php endpoint accessible and the vulnerable parameter lacks input validation or output encoding.
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.
From vendor dataImplement input validation and output encoding on all user-supplied data in /admin/cloud.php. Use context-appropriate escaping and consider Content Security Policy headers to mitigate XSS risks.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3370 — 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-3370 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