<?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>Wed, 07 Oct 2026 23:34:33 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-281003</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-281003</link>
      <description>EUVD-2026-281003</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-281003</guid>
    </item>
    <item>
      <title>fkie_cve-2025-34078</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-34078</link>
      <description>&lt;p&gt;A local privilege escalation vulnerability exists in NSClient++ 0.5.2.35 when both the web interface and ExternalScripts features are enabled. The configuration file (nsclient.ini) stores the administrative password in plaintext and is readable by local users. By extracting this password, an attacker can authenticate to the NSClient++ web interface (typically accessible on port 8443) and abuse the ExternalScripts plugin to inject and execute arbitrary commands as SYSTEM by registering a custom script, saving the configuration, and triggering it via the API.&lt;/p&gt;
&lt;p&gt;This behavior is documented but insecure, as the plaintext credential exposure undermines access isolation between local users and administrative functions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A local privilege escalation vulnerability exists in NSClient++ 0.5.2.35 when both the web interface and ExternalScripts features are enabled. The configuration file (nsclient.ini) stores the administrative password in plaintext and is readable by local users. By extracting this password, an attacker can authenticate to the NSClient++ web interface (typically accessible on port 8443) and abuse the ExternalScripts plugin to inject and execute arbitrary commands as SYSTEM by registering a custom script, saving the configuration, and triggering it via the API.&lt;/p&gt;
&lt;p&gt;This behavior is documented but insecure, as the plaintext credential exposure undermines access isolation between local users and administrative functions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-34078</guid>
    </item>
    <item>
      <title>GHSA-jr25-22p3-gm6r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jr25-22p3-gm6r</link>
      <description>&lt;p&gt;A local privilege escalation vulnerability exists in NSClient++ 0.5.2.35 when both the web interface and ExternalScripts features are enabled. The configuration file (nsclient.ini) stores the administrative password in plaintext and is readable by local users. By extracting this password, an attacker can authenticate to the NSClient++ web interface (typically accessible on port 8443) and abuse the ExternalScripts plugin to inject and execute arbitrary commands as SYSTEM by registering a custom script, saving the configuration, and triggering it via the API.&lt;/p&gt;
&lt;p&gt;This behavior is documented but insecure, as the plaintext credential exposure undermines access isolation between local users and administrative functions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A local privilege escalation vulnerability exists in NSClient++ 0.5.2.35 when both the web interface and ExternalScripts features are enabled. The configuration file (nsclient.ini) stores the administrative password in plaintext and is readable by local users. By extracting this password, an attacker can authenticate to the NSClient++ web interface (typically accessible on port 8443) and abuse the ExternalScripts plugin to inject and execute arbitrary commands as SYSTEM by registering a custom script, saving the configuration, and triggering it via the API.&lt;/p&gt;
&lt;p&gt;This behavior is documented but insecure, as the plaintext credential exposure undermines access isolation between local users and administrative functions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jr25-22p3-gm6r</guid>
    </item>
  </channel>
</rss>
