Skip to content
Fencer Vulns
medium 6.1

CVE-2025-36558 json

KUNBUS Revolution Pi Improper Neutralization of Server-Side Includes (SSI) Within a Web Page

published 2025-05-01 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-13267

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
21.1%
EPSS 21.1% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

KUNBUS PiCtory version 2.11.1 and earlier are vulnerable to a cross-site-scripting attack via the sso_token used for authentication. If an attacker provides the user with a PiCtory URL containing an HTML script as an sso_token, that script will reply to the user and be executed.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-25-121-01 updated cvss 6.1

KUNBUS GmbH Revolution Pi (Update A)

  • KUNBUS Revolution Pi PiCtory <=2.11.1
    affected: mitigation “KUNBUS has identified the following specific mitigations that users can apply to reduce risk:” kunbus.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

21.11% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA 4.0 5.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA 4.0 5.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • KUNBUS GmbH Revolution Pi PiCtory

Classification

Weakness
  • CWE-97 Improper Neutralization of Server-Side Includes (SSI) Within a Web Page

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.