<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T02:13:45.567064+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-77606</id>
    <title>fkie_cve-2026-77606</title>
    <updated>2026-10-05T02:13:45.570524+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Semantic MediaWiki is a free, open-source extension to MediaWiki that lets users store and query data within the wiki's pages. Prior to version 7.2.0, when `headers=plain`, table header text was emitted into `&lt;th&gt;` via a raw HTML path. User-controlled `mainlabel` content could therefore become executable HTML. Version 7.2.0 fixes the issue.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-77606"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-3jp5-3h47-28qf</id>
    <title>GHSA-3jp5-3h47-28qf — Semantic MediaWiki has reflected XSS in Special:Ask plain table headers</title>
    <updated>2026-10-05T02:13:45.570764+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: mediawiki/semantic-media-wiki</p>
<p>#### Failure mode</p>
<p>When `headers=plain`, table header text was emitted into `&lt;th&gt;` via a raw HTML path. User-controlled `mainlabel` content could therefore become executable HTML.</p>
<p>#### Remediation</p>
<p>- `TableResultPrinter` now applies output-context escaping before passing plain headers to the table renderer.
- The fix is limited to the HTML/plain-header branch so safe rendering modes are unaffected.</p>
<p>#### Why this is the right layer</p>
<p>The header value is not a structural token; it is display data. Sanitizing it at the sink is correct because the renderer owns the final HTML emission.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-3jp5-3h47-28qf"/>
  </entry>
</feed>
