Quaonos Schema ST4 example templates prone to XSS
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Quanos "SCHEMA ST4" example web templates in version Bootstrap 2019 v2/2021 v1/2022 v1/2022 SP1 v1 or below are prone to JavaScript injection allowing a remote attacker to hijack existing sessions to e.g. other web services in the same environment or execute scripts in the users browser environment. The affected script is '*-schema.js'.
- Published
- Dec 14, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 40th percentile
- CWE
- CWE-79
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 6.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| weidmueller | 19 iot md01 lan h4 s0011 firmware | cpe:2.3:o:weidmueller:19_iot_md01_lan_h4_s0011_firmware |
| weidmueller | 19 iot md01 lan h4 s0011 | cpe:2.3:h:weidmueller:19_iot_md01_lan_h4_s0011 |
| weidmueller | fp iot md01 4eu s2 00000 firmware | cpe:2.3:o:weidmueller:fp_iot_md01_4eu_s2_00000_firmware |
| weidmueller | fp iot md01 4eu s2 00000 | cpe:2.3:h:weidmueller:fp_iot_md01_4eu_s2_00000 |
| weidmueller | fp iot md01 lan s2 00000 firmware | cpe:2.3:o:weidmueller:fp_iot_md01_lan_s2_00000_firmware |
| weidmueller | fp iot md01 lan s2 00000 | cpe:2.3:h:weidmueller:fp_iot_md01_lan_s2_00000 |
| weidmueller | fp iot md01 lan s2 00011 firmware | cpe:2.3:o:weidmueller:fp_iot_md01_lan_s2_00011_firmware |
| weidmueller | fp iot md01 lan s2 00011 | cpe:2.3:h:weidmueller:fp_iot_md01_lan_s2_00011 |
| weidmueller | fp iot md02 4eu s3 00000 firmware | cpe:2.3:o:weidmueller:fp_iot_md02_4eu_s3_00000_firmware |
| weidmueller | fp iot md02 4eu s3 00000 | cpe:2.3:h:weidmueller:fp_iot_md02_4eu_s3_00000 |
| weidmueller | iot-gw30 firmware | cpe:2.3:o:weidmueller:iot-gw30_firmware |
| weidmueller | iot-gw30 | cpe:2.3:h:weidmueller:iot-gw30 |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- weidmueller 19 iot md01 lan h4 s0011 firmwareall versions
- weidmueller fp iot md01 4eu s2 00000 firmwareall versions
- weidmueller fp iot md01 lan s2 00000 firmwareall versions
- weidmueller fp iot md01 lan s2 00011 firmwareall versions
- weidmueller fp iot md02 4eu s3 00000 firmwareall versions
- weidmueller iot-gw30 firmwareup to 1.16.0 inclusive
- weidmueller iot-gw30-4g-eu firmwareup to 1.16.0 inclusive
- weidmueller uc20-wl2000-ac firmwareup to 1.16.0 inclusive
- weidmueller uc20-wl2000-iot firmwareup to 1.16.0 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
Quanos Schema ST4 example web templates
- 1affected
- 1 and later · up to and including 2affected · semver
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd-secondary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.