Security readout for executives and security teams
Plain-English summary
CVE-2019-14315 is a reported cross-site scripting issue in SunHater KCFinder. If an affected upload page is reachable, a remote attacker may cause attacker-controlled script or HTML to run in a user’s browser. The source bundle does not provide CVSS scoring, confirmed patch details, or evidence of active exploitation.
Executive priority
Treat this as a targeted legacy web application risk. It is not marked as actively exploited in the provided data, but exposed file-manager components can create meaningful session and data-access risk. Prioritize internet-facing or authenticated administrative deployments first.
Technical view
The vulnerability is described in upload.php in SunHater KCFinder 3.20-test1, 3.20-test2, 3.12, and earlier. The reported injection point is the CKEditorFuncNum parameter. Public data identifies it as XSS but does not include a CWE, CVSS vector, vendor advisory, or remediation version.
Likely exposure
Exposure is likely limited to applications that embed affected SunHater KCFinder versions and expose upload.php to users or the internet. Bundled or vendored KCFinder copies in CMS, editor, or legacy web apps should be checked because the CVE affected data is incomplete.
Exploitation context
The CVE states remote attackers can inject arbitrary web script or HTML. CISA KEV status is false in the provided bundle, and no cited source confirms exploitation in the wild. Practical impact depends on who can reach the vulnerable page and what privileges their browser session has.
Researcher notes
Evidence is sparse: the CVE description and GitHub issue identify the affected component, versions, and parameter, but not a CVSS score, CWE, patch version, or exploitation evidence. Validate exposure by inventory and reachability rather than assuming all CKEditor deployments are affected.
Mitigation direction
- Identify and replace affected KCFinder versions where vendor guidance supports it.
- Check the upstream issue and project releases for confirmed remediation details.
- Restrict access to upload.php where it is not required publicly.
- Apply server-side input validation and browser-safe output encoding for affected parameters.
- Monitor for suspicious requests targeting upload.php and CKEditorFuncNum.
Validation and detection
- Inventory web applications for SunHater KCFinder and vendored KCFinder copies.
- Compare discovered versions against 3.20-test1, 3.20-test2, 3.12, and earlier.
- Confirm whether upload.php is reachable from untrusted networks or users.
- Review application logs for unusual upload.php requests involving CKEditorFuncNum.
- Verify any remediation against vendor or upstream project guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-14315 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/sunhater/kcfinder/issues/180CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.