<?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://vulnerability.circl.lu</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:00:27 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-25744</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-25744</link>
      <description>&lt;p&gt;OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.0.0.2, the encounter vitals API accepts an `id` in the request body and treats it as an UPDATE. There is no verification that the vital belongs to the current patient or encounter. An authenticated user with encounters/notes permission can overwrite any patient&amp;#39;s vitals by supplying another patient&amp;#39;s vital `id`, leading to medical record tampering. Version 8.0.0.2 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.0.0.2, the encounter vitals API accepts an `id` in the request body and treats it as an UPDATE. There is no verification that the vital belongs to the current patient or encounter. An authenticated user with encounters/notes permission can overwrite any patient&amp;#39;s vitals by supplying another patient&amp;#39;s vital `id`, leading to medical record tampering. Version 8.0.0.2 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-25744</guid>
    </item>
  </channel>
</rss>
