GHSA-5724-X3RH-5QQQ

Vulnerability from github – Published: 2026-04-01 00:24 – Updated: 2026-04-01 00:24
VLAI
Summary
YesWiki has Multiple Reflected Cross-site Scripting Vulnerabilities
Details

Summary

Multiple reflected Cross-site Scripting (XSS) vulnerabilities across both authenticated and unauthenticated portions of the application. These findings present a significant security risk, as they can be leveraged to execute arbitrary JavaScript in a victim’s browser under various contexts.

Impact and Exploitation

While XSS is often treated as a standalone issue, these vulnerabilities have broader implications. Specifically, they can be used as launch points to exploit other significant vulnerabilities.

Proof of concept links follow. All testing was performed on my local docker setup running the lastest version of the application.

Proof of Concepts

Authenticated Reflected XSS

http://localhost:8085/?ElizabethJFeinler/deletepage&incomingurl=%22%3E%3Cscript%3Ealert(1)%3C%2fscript%3E
http://localhost:8085/?BazaR&vue=saisir&action=saisir_fiche&id=%3Cscript%3Ealert(1)%3C%2fscript%3E
http://localhost:8085/?GererThemes/upload&file=%3Cscript%3Ealert(1)%3C/script%3E

Unauthenticated Reflected XSS

http://localhost:8085/?PagePrincipale/listpages&tags=%22%3E%3Cscript%3Ealert(1)%3C/script%3E

In this one, most of the parameters can be used to deliver an XSS payload, not just the template parameter.

http://localhost:8085/?BazaR/bazariframe&id=2&template=<script>alert(1)</script>&width=100%25&height=600px&lat=46.22763&lon=2.213749&markersize=big&provider=MapBox&zoom=5&groups=&titles=&groupsexpanded=false

Impact

The reflected XSS vulnerabilities identified pose a significant risk to both application integrity and user safety. When combined with other issues discovered such as insecure endpoints or improper authentication mechanisms. These XSS flaws can be leveraged to escalate access, hijack sessions, and in some cases, achieve remote code execution (RCE). For example, malicious JavaScript executed via XSS could be used to trigger authenticated requests that exploit backend vulnerabilities, ultimately allowing an attacker to execute arbitrary commands on the server or pivot deeper into the environment.

Mitigation

Update to version 4.6.0

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "yeswiki/yeswiki"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.6.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-01T00:24:13Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "### Summary\n\nMultiple **reflected Cross-site Scripting (XSS)** vulnerabilities across both **authenticated and unauthenticated** portions of the application. These findings present a significant security risk, as they can be leveraged to execute arbitrary JavaScript in a victim\u2019s browser under various contexts.\n\n## Impact and Exploitation\n\nWhile XSS is often treated as a standalone issue, these vulnerabilities have broader implications. Specifically, they can be used as **launch points to exploit other significant vulnerabilities**. \n\nProof of concept links follow. All testing was performed on my local docker setup running the lastest version of the application. \n\n## Proof of Concepts\n\n## Authenticated Reflected XSS\n\n```\nhttp://localhost:8085/?ElizabethJFeinler/deletepage\u0026incomingurl=%22%3E%3Cscript%3Ealert(1)%3C%2fscript%3E\n```\n\n```\nhttp://localhost:8085/?BazaR\u0026vue=saisir\u0026action=saisir_fiche\u0026id=%3Cscript%3Ealert(1)%3C%2fscript%3E\n```\n\n```\nhttp://localhost:8085/?GererThemes/upload\u0026file=%3Cscript%3Ealert(1)%3C/script%3E\n```\n\n## Unauthenticated Reflected XSS\n\n\n```\nhttp://localhost:8085/?PagePrincipale/listpages\u0026tags=%22%3E%3Cscript%3Ealert(1)%3C/script%3E\n```\n\nIn this one, most of the parameters can be used to deliver an XSS payload, not just the template parameter. \n\n```\nhttp://localhost:8085/?BazaR/bazariframe\u0026id=2\u0026template=\u003cscript\u003ealert(1)\u003c/script\u003e\u0026width=100%25\u0026height=600px\u0026lat=46.22763\u0026lon=2.213749\u0026markersize=big\u0026provider=MapBox\u0026zoom=5\u0026groups=\u0026titles=\u0026groupsexpanded=false\n```\n\n### Impact\n\nThe reflected XSS vulnerabilities identified pose a significant risk to both application integrity and user safety. When combined with other issues discovered such as insecure endpoints or improper authentication mechanisms. These XSS flaws can be leveraged to escalate access, hijack sessions, and in some cases, achieve remote code execution (RCE). For example, malicious JavaScript executed via XSS could be used to trigger authenticated requests that exploit backend vulnerabilities, ultimately allowing an attacker to execute arbitrary commands on the server or pivot deeper into the environment.\n\n### Mitigation\nUpdate to version 4.6.0",
  "id": "GHSA-5724-x3rh-5qqq",
  "modified": "2026-04-01T00:24:13Z",
  "published": "2026-04-01T00:24:13Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/YesWiki/yeswiki/security/advisories/GHSA-5724-x3rh-5qqq"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/YesWiki/yeswiki"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "YesWiki has Multiple Reflected Cross-site Scripting Vulnerabilities"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…