<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-09T14:13:37.103649+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cnvd-2018-08808</id>
    <title>cnvd-2018-08808</title>
    <updated>2026-10-09T14:13:37.137267+00:00</updated>
    <content>cnvd-2018-08808</content>
    <link href="https://db.gcve.eu/vuln/cnvd-2018-08808"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2018-6182</id>
    <title>fkie_cve-2018-6182</title>
    <updated>2026-10-09T14:13:37.137315+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Mahara 16.10 before 16.10.9 and 17.04 before 17.04.7 and 17.10 before 17.10.4 are vulnerable to bad input when TinyMCE is bypassed by POST packages. Therefore, Mahara should not rely on TinyMCE's code stripping alone but also clean input on the server / PHP side as one can create own packets of POST data containing bad content with which to hit the server.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2018-6182"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-j7qh-wjjv-qxg8</id>
    <title>GHSA-j7qh-wjjv-qxg8</title>
    <updated>2026-10-09T14:13:37.137353+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Mahara 16.10 before 16.10.9 and 17.04 before 17.04.7 and 17.10 before 17.10.4 are vulnerable to bad input when TinyMCE is bypassed by POST packages. Therefore, Mahara should not rely on TinyMCE's code stripping alone but also clean input on the server / PHP side as one can create own packets of POST data containing bad content with which to hit the server.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-j7qh-wjjv-qxg8"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/gsd-2018-6182</id>
    <title>gsd-2018-6182</title>
    <updated>2026-10-09T14:13:37.137372+00:00</updated>
    <content>gsd-2018-6182</content>
    <link href="https://db.gcve.eu/vuln/gsd-2018-6182"/>
  </entry>
</feed>
