CVE-2020-18035
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 · uneditedCross Site Scripting (XSS) in Jeesns v1.4.2 allows remote attackers to execute arbitrary code by injecting commands into the "CKEditorFuncNum" parameter in the component "CkeditorUploadController.java".
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 confidenceA reflected Cross Site Scripting (XSS) vulnerability exists in Jeesns v1.4.2 within the CkeditorUploadController.java component. The CKEditorFuncNum parameter is not properly sanitized, allowing attackers to inject malicious JavaScript that executes in victims' browsers when the parameter value is reflected in the response.
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.4.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.
-
Identify if Jeesns is installedLook for Jeesns web application files in your web server directory or check HTTP response headers for Jeesns identifiersAffected if The application is the Jeesns web application
-
Confirm Jeesns version is 1.4.2Check the application's version file, about page, or API endpoint that exposes version information, then compare against the affected version = 1.4.2Affected if The installed version is exactly 1.4.2
-
Locate CkeditorUploadController componentCheck if the /ckeditor/upload or similar CKEditor upload endpoint exists in the web application by reviewing deployed Java/JSP files or checking accessible URL routesAffected if The CkeditorUploadController component is deployed and accessible
-
Verify CKEditorFuncNum parameter handlingSend a test request to the CKEditor upload endpoint with a crafted CKEditorFuncNum parameter containing a benign test payload (e.g., <script>alert(1)</script>), then inspect the HTTP response to see if the parameter value is reflected without encoding or sanitizationAffected if The CKEditorFuncNum parameter value is reflected in the response without proper output encoding, indicating the vulnerability is present
You are affected if Jeesns version 1.4.2 is installed and the CKEditorFuncNum parameter in the CkeditorUploadController is reflected in the HTTP response without sanitization, allowing script injection.
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 for the CKEditorFuncNum parameter. Apply context-appropriate output encoding when the parameter value is used in HTTP responses to prevent script execution.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-18035 — 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-18035 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