CVE-2026-39667
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Jongmyoung Kim Korea SNS korea-sns allows DOM-Based XSS.This issue affects Korea SNS: from n/a through <= 1.7.0.
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 confidenceDOM-based Cross-site Scripting (XSS) vulnerability in Korea SNS where user-supplied input is not properly neutralized before being inserted into the DOM, allowing attackers to inject malicious JavaScript that executes in the victim's browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
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 the affected applicationIdentify if the web application in use is Korea SNS or a related Korean social networking platform. Check application name, branding, or documentation.Affected if The application is Korea SNS or a variant of Korean social networking software.
-
Identify user input entry pointsLocate all forms, comment fields, profile fields, messaging features, or URL parameters that accept user-provided text and render it back in the page.Affected if The application contains fields where users can submit text content that is displayed on web pages.
-
Inspect DOM rendering for unsanitized outputUse browser developer tools (Elements panel) to examine how submitted input appears in the page source. Look for user data rendered inside HTML tags, JavaScript variables, or inline event handlers without encoding.Affected if User input appears in the DOM as raw text inside HTML attributes, script blocks, or event handlers without proper HTML encoding (e.g., < becomes <).
-
Test for XSS payload reflectionSubmit a test XSS payload such as <script>alert(1)</script> or <img src=x onerror=alert(1)> in identified input fields. Examine if the payload executes or appears unescaped in the page.Affected if The submitted payload renders as executable JavaScript or appears unescaped in the page source.
-
Check source code for output encodingReview JavaScript or server-side code that handles user input and outputs it to pages. Verify if encoding functions (such as htmlEscape, encodeForHTML, or equivalent) are used before inserting user data into the DOM.Affected if No output encoding or sanitization functions are applied to user input before DOM insertion.
If Korea SNS is in use and user-submitted content is rendered in the browser DOM without proper HTML or JavaScript encoding, the environment is affected by this DOM-based 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 dataImplement proper input validation and output encoding in client-side JavaScript code that handles user input; specifically sanitize or encode all data before inserting it into the HTML document.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39667 — 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-2026-39667 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