CVE-2020-11626
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 · uneditedAn issue was discovered in EJBCA before 6.15.2.6 and 7.x before 7.3.1.2. Two Cross Side Scripting (XSS) vulnerabilities have been found in the Public Web and the Certificate/CRL download servlets.
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 confidenceTwo Cross-Site Scripting (XSS) vulnerabilities in EJBCA's Public Web servlet and Certificate/CRL download servlets allow attackers to inject malicious scripts via web requests. The vulnerabilities affect EJBCA versions before 6.15.2.6 and 7.x before 7.3.1.2.
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< 6.15.2.6>= 7.0.0, < 7.3.1.2CVSS 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.
-
Confirm EJBCA installationIdentify if Primekey EJBCA is installed on the system by checking for EJBCA installation directories (commonly under /opt/ejbca, $JBOSS_HOME, or application server deployments), or by querying running services for EJBCA-related Java processes.Affected if EJBCA is not present on the system, so the CVE does not apply.
-
Locate EJBCA version informationFind the installed EJBCA version. Common locations include: version.properties or ejbca.ear/META-INF/MANIFEST.MF in the deployment directory, the EJBCA admin web interface (About page), or the database if configured.Affected if Unable to determine the installed version.
-
Compare version against affected rangesCompare the installed version to the affected ranges: versions before 6.15.2.6, or versions 7.0.0 through 7.3.1.1 (inclusive).Affected if Installed version is 6.15.2.6 or higher, OR 7.3.1.2 or higher, meaning the version is not in the affected ranges.
-
Verify Public Web servlet accessibilityCheck if the EJBCA Public Web servlet is enabled and externally accessible. This servlet is typically accessible at paths like /ejbca/publicweb/ or /publicweb/ on the configured web server or application server.Affected if The Public Web servlet is exposed and the installed version falls within the affected ranges.
-
Verify Certificate/CRL download servlet accessibilityCheck if the Certificate/CRL download servlets are enabled and accessible. These are typically exposed at endpoints such as /ejbca/est/ or /ejbca/certreq/ or similar download endpoints.Affected if The Certificate/CRL download servlets are exposed and the installed version falls within the affected ranges.
If EJBCA is installed, the version is below 6.15.2.6 or between 7.0.0 and 7.3.1.1 inclusive, and the Public Web or Certificate/CRL servlets are accessible, the environment is affected by this XSS vulnerability.
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 data6.15.2.67.3.1.2
Upgrade EJBCA to version 6.15.2.6, 7.3.1.2, or later to remediate the XSS vulnerabilities.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11626 — 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-2020-11626 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