<?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>Fri, 23 Oct 2026 09:30:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-260498</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-260498</link>
      <description>EUVD-2026-260498</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-260498</guid>
    </item>
    <item>
      <title>fkie_cve-2025-62780</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-62780</link>
      <description>&lt;p&gt;changedetection.io is a free open source web page change detection tool. A Stored Cross Site Scripting is present in changedetection.io Watch update API in versions prior to 0.50.34 due to insufficient security checks. Two scenarios are possible. In the first, an attacker can insert a new watch with an arbitrary URL which really points to a web page. Once the HTML content is retrieved, the attacker updates the URL with a JavaScript payload. In the second, an attacker substitutes the URL in an existing watch with a new URL that is in reality a JavaScript payload. When the user clicks on *Preview* and then on the malicious link, the JavaScript malicious code is executed. Version 0.50.34 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;changedetection.io is a free open source web page change detection tool. A Stored Cross Site Scripting is present in changedetection.io Watch update API in versions prior to 0.50.34 due to insufficient security checks. Two scenarios are possible. In the first, an attacker can insert a new watch with an arbitrary URL which really points to a web page. Once the HTML content is retrieved, the attacker updates the URL with a JavaScript payload. In the second, an attacker substitutes the URL in an existing watch with a new URL that is in reality a JavaScript payload. When the user clicks on *Preview* and then on the malicious link, the JavaScript malicious code is executed. Version 0.50.34 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-62780</guid>
    </item>
    <item>
      <title>GHSA-4c3j-3h7v-22q9 — changedetection.io: Stored XSS in Watch update via API</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4c3j-3h7v-22q9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: changedetection.io&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A Stored Cross Site Scripting is present in the changedetection.io Watch update API due to unsufficient security checks.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Tested on changedetection.io version *v0.50.24*&lt;/p&gt;
&lt;p&gt;```console
REPOSITORY                            TAG       IMAGE ID       CREATED        SIZE
ghcr.io/dgtlmoon/changedetection.io   latest    0367276509a0   23 hours ago   599MB
```&lt;/p&gt;
&lt;p&gt;When a user tries to add an unsafe URL as a Watch in the changedetection.io UI, the action is blocked with the error message &amp;#34;Watch protocol is not permitted by SAFE_PROTOCOL_REGEX or incorrect URL format&amp;#34;.
This is catched by the function `validate_url(test_url)`.&lt;/p&gt;
&lt;p&gt;```python
def validate_url(test_url):
    # ...
    from .model.Watch import is_safe_url
    if not is_safe_url(test_url):
        # This should be wtforms.validators.
        raise ValidationError(&amp;#39;Watch protocol is not permitted by SAFE_PROTOCOL_REGEX or incorrect URL format&amp;#39;)
```&lt;/p&gt;
&lt;p&gt;When instead the Watch API is used, this check is not performed resulting in unsafe URLs added as Watch.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Update an existing watch with an unsafe URL
```console
curl -X PUT &amp;#34;http://example.site/api/v1/watch/1242e1c5-d59e-4352-0078-203a55b21282&amp;#34; \
  -H &amp;#34;x-api-key: XXX&amp;#34; \
  -H &amp;#34;Content-Type: application/json&amp;#34; \
  -d &amp;#39;{
    &amp;#34;url&amp;#34;: &amp;#34;javascript:alert(document.domain)&amp;#34;,
    &amp;#34;title&amp;#34;: &amp;#34;XSS PoC&amp;#34;,
    &amp;#34;paused&amp;#34;: false
  }&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Two scenarios are possibile:&lt;/p&gt;
&lt;p&gt;1. An attacker can insert a new watch with an arbitrary URL which really points to a web page. O…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: changedetection.io&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A Stored Cross Site Scripting is present in the changedetection.io Watch update API due to unsufficient security checks.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Tested on changedetection.io version *v0.50.24*&lt;/p&gt;
&lt;p&gt;```console
REPOSITORY                            TAG       IMAGE ID       CREATED        SIZE
ghcr.io/dgtlmoon/changedetection.io   latest    0367276509a0   23 hours ago   599MB
```&lt;/p&gt;
&lt;p&gt;When a user tries to add an unsafe URL as a Watch in the changedetection.io UI, the action is blocked with the error message &amp;#34;Watch protocol is not permitted by SAFE_PROTOCOL_REGEX or incorrect URL format&amp;#34;.
This is catched by the function `validate_url(test_url)`.&lt;/p&gt;
&lt;p&gt;```python
def validate_url(test_url):
    # ...
    from .model.Watch import is_safe_url
    if not is_safe_url(test_url):
        # This should be wtforms.validators.
        raise ValidationError(&amp;#39;Watch protocol is not permitted by SAFE_PROTOCOL_REGEX or incorrect URL format&amp;#39;)
```&lt;/p&gt;
&lt;p&gt;When instead the Watch API is used, this check is not performed resulting in unsafe URLs added as Watch.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Update an existing watch with an unsafe URL
```console
curl -X PUT &amp;#34;http://example.site/api/v1/watch/1242e1c5-d59e-4352-0078-203a55b21282&amp;#34; \
  -H &amp;#34;x-api-key: XXX&amp;#34; \
  -H &amp;#34;Content-Type: application/json&amp;#34; \
  -d &amp;#39;{
    &amp;#34;url&amp;#34;: &amp;#34;javascript:alert(document.domain)&amp;#34;,
    &amp;#34;title&amp;#34;: &amp;#34;XSS PoC&amp;#34;,
    &amp;#34;paused&amp;#34;: false
  }&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Two scenarios are possibile:&lt;/p&gt;
&lt;p&gt;1. An attacker can insert a new watch with an arbitrary URL which really points to a web page. O…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4c3j-3h7v-22q9</guid>
    </item>
    <item>
      <title>PYSEC-2025-91</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2025-91</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: changedetection-io&lt;/p&gt;
&lt;p&gt;changedetection.io is a free open source web page change detection tool. A Stored Cross Site Scripting is present in changedetection.io Watch update API in versions prior to 0.50.34 due to insufficient security checks. Two scenarios are possible. In the first, an attacker can insert a new watch with an arbitrary URL which really points to a web page. Once the HTML content is retrieved, the attacker updates the URL with a JavaScript payload. In the second, an attacker substitutes the URL in an existing watch with a new URL that is in reality a JavaScript payload. When the user clicks on *Preview* and then on the malicious link, the JavaScript malicious code is executed. Version 0.50.34 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: changedetection-io&lt;/p&gt;
&lt;p&gt;changedetection.io is a free open source web page change detection tool. A Stored Cross Site Scripting is present in changedetection.io Watch update API in versions prior to 0.50.34 due to insufficient security checks. Two scenarios are possible. In the first, an attacker can insert a new watch with an arbitrary URL which really points to a web page. Once the HTML content is retrieved, the attacker updates the URL with a JavaScript payload. In the second, an attacker substitutes the URL in an existing watch with a new URL that is in reality a JavaScript payload. When the user clicks on *Preview* and then on the malicious link, the JavaScript malicious code is executed. Version 0.50.34 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2025-91</guid>
    </item>
  </channel>
</rss>
