CVE-2017-14744
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 · uneditedUEditor 1.4.3.3 has XSS via the SRC attribute of an IFRAME element.
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 confidenceUEditor 1.4.3.3 contains a stored or reflected cross-site scripting (XSS) vulnerability allowing attackers to inject malicious JavaScript via the SRC attribute of an IFRAME element. This could enable session hijacking, credential theft, or malware delivery through the compromised editor.
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.3.3CVSS 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.0/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 UEditor versionLocate the UEditor installation in your application and check its version file, version comment in source code, or version endpoint. Common locations include version.js, about page, or the UEditor config file.Affected if The installed version is 1.4.3.3 or any earlier version.
-
Verify iframe insertion is enabledCheck if the UEditor toolbar includes the iframe or media insertion button, or verify the editor configuration allows iframe elements in the allowed tags list.Affected if Iframe insertion capability is enabled and accessible to users.
-
Inspect stored editor content for malicious iframesSearch your database or content storage for any records containing iframe tags with suspicious SRC attributes, especially those using javascript: or data: protocols, or pointing to unknown external domains.Affected if Any stored content contains iframe elements with malicious or unexpected SRC attributes.
-
Test reflected XSS in iframe SRCIf you have editor access, create a test document and attempt to insert an iframe with a crafted SRC attribute (such as javascript:alert(1)) to confirm the vulnerability exists in your environment.Affected if The editor accepts and renders iframe elements with unsafe SRC content without sanitization.
Your environment is affected if you are running UEditor version 1.4.3.3 or earlier and the iframe insertion feature is accessible to users.
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 dataUpgrade to a patched version of UEditor if available; otherwise, implement strict input validation and sanitization on iframe SRC attributes, and apply context-aware output encoding to prevent script execution.
- 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-2017-14744 — 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-2017-14744 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