Vulnerabilities in pkg:nuget/YAFNET.Core

PACKAGE
Advisory Identifier: GHSA-8rq5-wwpp-fmj2
Advisory Summary

CVE-2026-43939 is a HIGH (CVSS 7.3) cross-site scripting vulnerability (CWE-116: Improper Encoding or Escaping of Output) affecting YAFNET.Core libraries in the NuGet ecosystem. The issue involves yafnet has stored xss in forum thread posts/replies that allows arbitrary javascript execution for all thread viewers. Remediation is available by upgrading affected packages to version 4.0.5, 3.2.12.

3 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:nuget/YAFNET.Core

3 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:nuget/YAFNET.Core. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-8rq5-wwpp-fmj2 CVE-2026-43939 HIGH YAFNET has Stored XSS in Forum Thread Posts/Replies that Allows Arbitrary JavaScript Execution for All Thread Viewers
GHSA-xhw7-j96h-c3g5 CVE-2026-43937 HIGH YAFNET: Pre-Handler Authorization Bypass on Admin Pages Enables Blind SQL Execution via `/Admin/RunSql`
GHSA-33gv-fc78-qgf5 CVE-2026-43938 HIGH YAFNET has Unauthenticated Stored Second-Order XSS in Admin Event Log via Reflected `User-Agent` Header

CVE-2026-43939 at a Glance

CVE Identifier CVE-2026-43939
GHSA Identifier GHSA-8rq5-wwpp-fmj2
Severity HIGH
CVSS v3.1 Base Score 7.3
CWE Classification CWE-116: Improper Encoding or Escaping of Output
Affected Product YAFNET.Core
Package Ecosystem NuGet
Published Date
Last Updated

Security Impact

CVSS: 7.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-43939

To remediate this vulnerability, upgrade all affected YAFNET.Core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

YAFNET.Core fixed: 4.0.5
Upgrade YAFNET.Core to 4.0.5
YAFNET.Core fixed: 3.2.12
Upgrade YAFNET.Core to 3.2.12
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for YAFNET.Core

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-43939, inspect your project dependencies for YAFNET.Core:

inspect dependencies for YAFNET.Core

Analyze the terminal output to locate any version of YAFNET.Core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.0.5), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-116: Improper Encoding or Escaping of Output, where the product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. as a result, the intended structure of the message is not preserved. In YAFNET.Core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

**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 `"><img src=x onerror=prompt(0)>` causes the payload to break out of the surrounding HTML context and inject a fully attacker-controlled `<img>` 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-cookie theft, account takeover through same-origin state-changing requests, forced privileged actions if an administrator views the thread, credential phishing via injected login overlays, forum defacement, cryptominer or malware delivery, and mass redirection of viewers to attacker-controlled sites. Because the payload triggers automatically on page load rather than requiring hover or click interaction, a single malicious post can compromise a large number of users very quickly. **Likelihood:** Exploitation requires only a registered account with permission to post or reply, which is available to every forum member by default. Once posted, the payload fires automatically for any visitor who opens the thread, requiring zero victim interaction and making the overall likelihood high. **Steps to Reproduce:** - Log in to the forum as any low-privileged user (Attacker). - Navigate to any thread where posting or replying is allowed, or create a new thread. - In the post/reply body, submit the payload: `"><img src=x onerror=prompt(0)>` - Publish the post or reply. - Log in as a different user (e.g., Admin) or visit the thread in a separate browser session. - Open the thread page, the injected `<img>` fails to load and the `onerror` handler fires, producing a `prompt(0)` dialog and confirming arbitrary JavaScript execution in the viewer's session context. <img width="1127" height="745" alt="image" src="https://github.com/user-attachments/assets/b93442ea-1d8e-4079-ab4f-e52d41d110f3" />

CVE-2026-43939 Affected YAFNET.Core Versions

2 component(s)
Fixed Versions:
4.0.53.2.12
Product / Package Ecosystem Affected Versions Fixed Version
YAFNET.Core
NuGet
≥ 4.0.0-beta01
< 4.0.5
4.0.5
YAFNET.Core
NuGet
< 3.2.12
3.2.12

References

Frequently Asked Questions

What is CVE-2026-43939?
CVE-2026-43939 is a security vulnerability in YAFNET.Core involving YAFNET has Stored XSS in Forum Thread Posts/Replies that Allows Arbitrary JavaScript Execution for All Thread Viewers under CWE-116: Improper Encoding or Escaping of Output.
Which YAFNET.Core versions are affected?
Affected versions include releases prior to 4.0.5, 3.2.12 across affected packages: YAFNET.Core.
What version fixes CVE-2026-43939?
Upgrading to 4.0.5, 3.2.12 (or the latest patched release for your respective branch) resolves the vulnerability.
Is YAFNET.Core affected?
Yes, YAFNET.Core is affected in releases prior to 4.0.5, 3.2.12. Upgrade your dependency to 4.0.5, 3.2.12 or later.
What is the CVSS score of CVE-2026-43939?
CVE-2026-43939 has a CVSS v3.1 base score of 7.3 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-43939?
CVE-2026-43939 is classified under CWE-116: Improper Encoding or Escaping of Output (The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.).
How can I check NuGet dependencies for CVE-2026-43939?
Run the dependency tree command: 'inspect dependencies for YAFNET.Core'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8rq5-wwpp-fmj2",
  "modified" : "2026-05-13T16:24:29Z",
  "published" : "2026-05-05T20:32:47Z",
  "aliases" : [ "CVE-2026-43939" ],
  "summary" : "YAFNET has Stored XSS in Forum Thread Posts/Replies that Allows Arbitrary JavaScript Execution for All Thread Viewers",
  "details" : "**Description:**\nStored 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.\n\n**Issue Details:**\nThe 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 `\"><img src=x onerror=prompt(0)>` causes the payload to break out of the surrounding HTML context and inject a fully attacker-controlled `<img>` 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.\n\n**Impact:**\nAn 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-cookie theft, account takeover through same-origin state-changing requests, forced privileged actions if an administrator views the thread, credential phishing via injected login overlays, forum defacement, cryptominer or malware delivery, and mass redirection of viewers to attacker-controlled sites. Because the payload triggers automatically on page load rather than requiring hover or click interaction, a single malicious post can compromise a large number of users very quickly.\n\n**Likelihood:**\nExploitation requires only a registered account with permission to post or reply, which is available to every forum member by default. Once posted, the payload fires automatically for any visitor who opens the thread, requiring zero victim interaction and making the overall likelihood high.\n\n**Steps to Reproduce:**\n- Log in to the forum as any low-privileged user (Attacker).\n- Navigate to any thread where posting or replying is allowed, or create a new thread.\n- In the post/reply body, submit the payload: `\"><img src=x onerror=prompt(0)>`\n- Publish the post or reply.\n- Log in as a different user (e.g., Admin) or visit the thread in a separate browser session.\n- Open the thread page, the injected `<img>` fails to load and the `onerror` handler fires, producing a `prompt(0)` dialog and confirming arbitrary JavaScript execution in the viewer's session context.\n<img width=\"1127\" height=\"745\" alt=\"image\" src=\"https://github.com/user-attachments/assets/b93442ea-1d8e-4079-ab4f-e52d41d110f3\" />",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "NuGet",
      "name" : "YAFNET.Core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0-beta01"
      }, {
        "fixed" : "4.0.5"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.0.4"
    }
  }, {
    "package" : {
      "ecosystem" : "NuGet",
      "name" : "YAFNET.Core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.2.12"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.2.11"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/YAFNET/YAFNET/security/advisories/GHSA-8rq5-wwpp-fmj2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-43939"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/YAFNET/YAFNET"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/YAFNET/YAFNET/releases/tag/v3.2.12"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/YAFNET/YAFNET/releases/tag/v4.0.5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-116", "CWE-79", "CWE-80" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-05T20:32:47Z",
    "nvd_published_at" : "2026-05-12T15:16:15Z"
  }
}