<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 23:59:47 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-265549</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-265549</link>
      <description>EUVD-2026-265549</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-265549</guid>
    </item>
    <item>
      <title>fkie_cve-2026-22704</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-22704</link>
      <description>&lt;p&gt;HAX CMS helps manage microsite universe with PHP or NodeJs backends. In versions 11.0.6 to before 25.0.0, HAX CMS is vulnerable to stored XSS, which could lead to account takeover. This issue has been patched in version 25.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;HAX CMS helps manage microsite universe with PHP or NodeJs backends. In versions 11.0.6 to before 25.0.0, HAX CMS is vulnerable to stored XSS, which could lead to account takeover. This issue has been patched in version 25.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-22704</guid>
    </item>
    <item>
      <title>GHSA-3fm2-xfq7-7778 — HAXcms Has Stored XSS Vulnerability that May Lead to Account Takeover</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3fm2-xfq7-7778</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @haxtheweb/haxcms-nodejs&lt;/p&gt;
&lt;p&gt;### Summary
Stored XSS Leading to Account Takeover&lt;/p&gt;
&lt;p&gt;### Details
The Exploit Chain:
1.Upload: The attacker uploads an `.html` file containing a JavaScript payload.
2.Execution: A logged-in administrator is tricked into visiting the URL of this uploaded file.
3.Token Refresh: The JavaScript payload makes a `fetch` request to the `/system/api/refreshAccessToken` endpoint. Because the administrator is logged in, their browser automatically attaches the `haxcms_refresh_token` cookie to this request.
4.JWT Theft: The server validates the refresh token and responds with a new, valid JWT access token in the JSON response.
5.Exfiltration: The JavaScript captures this new JWT from the response and sends it to an attacker-controlled server.
6.Account Takeover: The attacker now possesses a valid administrator JWT and can take full control of the application.&lt;/p&gt;
&lt;p&gt;Vulnerability recurrence:&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1198&amp;#34; height=&amp;#34;756&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/7062d542-702e-4cbe-8493-da0f71e790c3&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;Then we test access to this html&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1433&amp;#34; height=&amp;#34;1019&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/6c72c92f-a151-4b0e-b6ba-d83ffb771253&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;You can obtain other people&amp;#39;s identity information&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1082&amp;#34; height=&amp;#34;290&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/23398ea4-f08c-47bd-b2f1-89071af0e275&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;### PoC
POST /system/api/saveFile?siteName=yu&amp;amp;site_token=neWmRyvNbCCwiQ7MP2ojAjVMk-HtjlKYNOqsQjLt3RQ&amp;amp;jwt=eyJ0eXAiOiJKV1QiLCJh…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @haxtheweb/haxcms-nodejs&lt;/p&gt;
&lt;p&gt;### Summary
Stored XSS Leading to Account Takeover&lt;/p&gt;
&lt;p&gt;### Details
The Exploit Chain:
1.Upload: The attacker uploads an `.html` file containing a JavaScript payload.
2.Execution: A logged-in administrator is tricked into visiting the URL of this uploaded file.
3.Token Refresh: The JavaScript payload makes a `fetch` request to the `/system/api/refreshAccessToken` endpoint. Because the administrator is logged in, their browser automatically attaches the `haxcms_refresh_token` cookie to this request.
4.JWT Theft: The server validates the refresh token and responds with a new, valid JWT access token in the JSON response.
5.Exfiltration: The JavaScript captures this new JWT from the response and sends it to an attacker-controlled server.
6.Account Takeover: The attacker now possesses a valid administrator JWT and can take full control of the application.&lt;/p&gt;
&lt;p&gt;Vulnerability recurrence:&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1198&amp;#34; height=&amp;#34;756&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/7062d542-702e-4cbe-8493-da0f71e790c3&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;Then we test access to this html&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1433&amp;#34; height=&amp;#34;1019&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/6c72c92f-a151-4b0e-b6ba-d83ffb771253&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;You can obtain other people&amp;#39;s identity information&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1082&amp;#34; height=&amp;#34;290&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/23398ea4-f08c-47bd-b2f1-89071af0e275&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;### PoC
POST /system/api/saveFile?siteName=yu&amp;amp;site_token=neWmRyvNbCCwiQ7MP2ojAjVMk-HtjlKYNOqsQjLt3RQ&amp;amp;jwt=eyJ0eXAiOiJKV1QiLCJh…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3fm2-xfq7-7778</guid>
    </item>
  </channel>
</rss>
