<?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>Sat, 03 Oct 2026 08:21:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-276609</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-276609</link>
      <description>EUVD-2026-276609</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-276609</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32868</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32868</link>
      <description>&lt;p&gt;OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in the &amp;#39;My Information&amp;#39; screen. An authenticated attacker can inject parts of an XSS payload in the first and last name fields. The payload is executed when the full name is rendered. The attacker can run script in the context of a victim&amp;#39;s session.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in the &amp;#39;My Information&amp;#39; screen. An authenticated attacker can inject parts of an XSS payload in the first and last name fields. The payload is executed when the full name is rendered. The attacker can run script in the context of a victim&amp;#39;s session.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32868</guid>
    </item>
    <item>
      <title>GHSA-3g9r-2f6r-x6j2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3g9r-2f6r-x6j2</link>
      <description>&lt;p&gt;OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in the &amp;#39;My Information&amp;#39; screen. An authenticated attacker can inject parts of an XSS payload in the first and last name fields. The payload is executed when the full name is rendered. The attacker can run script in the context of a victim&amp;#39;s session.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in the &amp;#39;My Information&amp;#39; screen. An authenticated attacker can inject parts of an XSS payload in the first and last name fields. The payload is executed when the full name is rendered. The attacker can run script in the context of a victim&amp;#39;s session.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3g9r-2f6r-x6j2</guid>
    </item>
    <item>
      <title>VA-26-077-01 — OPEXUS eComplaint and eCase multiple vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/va-26-077-01</link>
      <description>&lt;p&gt;OPEXUS eComplaint and eCASE before version 10.1.0.0 include the secret verification code in the HTTP response when requesting a password reset via &amp;#39;ForcePasswordReset.aspx&amp;#39;. An attacker who knows an existing user&amp;#39;s email address can reset the user&amp;#39;s password and security questions. Existing security questions are not asked during the process. OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in a user profile. An authenticated attacker can inject parts of an XSS payload in their first and last name fields. The payload is executed when the user&amp;#39;s full name is rendered. The attacker can run script in the context of a victim&amp;#39;s session. OPEXUS eComplaint before version 10.1.0.0 allows an unauthenticated attacker to obtain or guess an existing case number and upload arbitrary files via &amp;#39;Portal/EEOC/DocumentUploadPub.aspx&amp;#39;. Users would see these unexpected files in cases. Uploading a large number of files could consume storage. OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in the &amp;#39;My Information&amp;#39; screen. An authenticated attacker can inject parts of an XSS payload in the first and last name fields. The payload is executed when the full name is rendered. The attacker can run script in the context of a victim&amp;#39;s session. OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of the &amp;#34;Name of Organization&amp;#34; field when filling out c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OPEXUS eComplaint and eCASE before version 10.1.0.0 include the secret verification code in the HTTP response when requesting a password reset via &amp;#39;ForcePasswordReset.aspx&amp;#39;. An attacker who knows an existing user&amp;#39;s email address can reset the user&amp;#39;s password and security questions. Existing security questions are not asked during the process. OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in a user profile. An authenticated attacker can inject parts of an XSS payload in their first and last name fields. The payload is executed when the user&amp;#39;s full name is rendered. The attacker can run script in the context of a victim&amp;#39;s session. OPEXUS eComplaint before version 10.1.0.0 allows an unauthenticated attacker to obtain or guess an existing case number and upload arbitrary files via &amp;#39;Portal/EEOC/DocumentUploadPub.aspx&amp;#39;. Users would see these unexpected files in cases. Uploading a large number of files could consume storage. OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in the &amp;#39;My Information&amp;#39; screen. An authenticated attacker can inject parts of an XSS payload in the first and last name fields. The payload is executed when the full name is rendered. The attacker can run script in the context of a victim&amp;#39;s session. OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of the &amp;#34;Name of Organization&amp;#34; field when filling out c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/va-26-077-01</guid>
    </item>
  </channel>
</rss>
