Categories
CVE-2026-43939 high CVSS 7.3

Vulnerability in YAFNET.Core (CVE-2026-43939)

Summary

Vulnerability in YAFNET.Core (CVE-2026-43939). Confidential information can be exposed externally. Exploitable via onerror. Mitigation: upgrade to 3.2.12 or later.

Original description

The description as published by the source.

Description:
Stored Cross-Site Scripting (XSS) occurs when user-supplied input is persisted by the application and later rendered in another user's browser without proper sanitization or contextual output encoding. When the vulnerable sink is a high-traffic surface such as a public forum thread, the payload executes in the browser of every user who visits the page, maximizing both reach and impact. Any JavaScript injected through such a sink runs under the application's origin and inherits the privileges of whichever user happens to view the affected content.

Issue Details:
The thread posting and reply feature accepts user-supplied content that is stored server-side and later rendered back into the thread page without adequate HTML sanitization or contextual output encoding. Submitting a post or reply containing "> causes the payload to break out of the surrounding HTML context and inject a fully attacker-controlled `` element whose onerror handler fires automatically as soon as the broken image reference fails to load. Because posts and replies are visible to every user who visits the thread, authenticated or otherwise, the injected JavaScript executes in each viewer's browser the moment the page renders, with no additional interaction required.

Impact:
An attacker with a standard forum account can execute arbitrary JavaScript in the browser of every user who loads the affected thread, including moderators and administrators. This enables session/auth-cooki…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-43939 has been found in YAFNET.Core.
Attackers can target a specific entry point like onerror over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.3/10.
What to do: upgrade YAFNET.Core to 3.2.12 or later.
If unsure, ask your IT team or search "YAFNET.Core CVE-2026-43939" on the vendor's site.

CVE-2026-43939 (YAFNET.Core) — CWE-116 / CVSS v3 7.3
Attack vector: remote (network-reachable)
Attack surface: onerror
Patched: 3.2.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-116) exists in YAFNET.Core. Attackers reach the vulnerable code path via onerror.

📍 Affected scope

Check the vendor advisory for the affected versions of YAFNET.Core. Attack surface: onerror.

🔥 Severity

Severity: High (CVSS 7.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.2.12.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'YAFNET.Core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'YAFNET.Core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で YAFNET.Core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade YAFNET.Core to 3.2.12

    ステージング環境で 3.2.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

nuget YAFNET.Core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.12"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details