CVE-2025-67013: The web management interface in ETL Systems Ltd DEXTRA Series ' Digital L-Band Distribution System v1.8 does not implement Cross-Site Reques
Noroxi assessment
Priority: Monitor (action score 26/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.16% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- 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
The web management interface in ETL Systems Ltd DEXTRA Series ' Digital L-Band Distribution System v1.8 does not implement Cross-Site Request Forgery (CSRF) protection mechanisms (no tokens, no Origin/Referer validation) on critical configuration endpoints.
- Published
- Dec 26, 2025
- Updated
- Oct 13, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-352
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 |
|---|---|---|
| etlsystems | d0116s1ula-22454 firmware | cpe:2.3:o:etlsystems:d0116s1ula-22454_firmware |
| etlsystems | d0116s1ula-22454 | cpe:2.3:h:etlsystems:d0116s1ula-22454 |
| etlsystems | d0116s1uia-22474 firmware | cpe:2.3:o:etlsystems:d0116s1uia-22474_firmware |
| etlsystems | d0116s1uia-22474 | cpe:2.3:h:etlsystems:d0116s1uia-22474 |
| etlsystems | c0401s1ula-22418 firmware | cpe:2.3:o:etlsystems:c0401s1ula-22418_firmware |
| etlsystems | c0401s1ula-22418 | cpe:2.3:h:etlsystems:c0401s1ula-22418 |
| etlsystems | c0801s1ula-22420 firmware | cpe:2.3:o:etlsystems:c0801s1ula-22420_firmware |
| etlsystems | c0801s1ula-22420 | cpe:2.3:h:etlsystems:c0801s1ula-22420 |
| etlsystems | c1601s1ula-22422 firmware | cpe:2.3:o:etlsystems:c1601s1ula-22422_firmware |
| etlsystems | c1601s1ula-22422 | cpe:2.3:h:etlsystems:c1601s1ula-22422 |
| etlsystems | c0401s1ula-22455 firmware | cpe:2.3:o:etlsystems:c0401s1ula-22455_firmware |
| etlsystems | c0401s1ula-22455 | cpe:2.3:h:etlsystems:c0401s1ula-22455 |
and 42 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- etlsystems c0401d1uia-22476 firmware1.8
- etlsystems c0401d1ula-22419 firmware1.8
- etlsystems c0401d1ula-22456 firmware1.8
- etlsystems c0401s1ula-22418 firmware1.8
- etlsystems c0401s1ula-22455 firmware1.8
- etlsystems c0801d1ula-22421 firmware1.8
- etlsystems c0801d1ula-22458 firmware1.8
- etlsystems c0801s1ula-22420 firmware1.8
- etlsystems c0801s1ula-22457 firmware1.8
- etlsystems c1601s1uia-22479 firmware1.8
- etlsystems c1601s1ula-22422 firmware1.8
- etlsystems c1601s1ula-22459 firmware1.8
- etlsystems d0104d1ula-22411 firmware1.8
- etlsystems d0104d1ula-22451 firmware1.8
- etlsystems d0104s1ula-22410 firmware1.8
- etlsystems d0104s1ula-22450 firmware1.8
- etlsystems d0108d1uia-22473 firmware1.8
- etlsystems d0108d1ula-22413 firmware1.8
- etlsystems d0108d1ula-22453 firmware1.8
- etlsystems d0108s1ula-22412 firmware1.8
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.
No history yet (it accumulates with the daily EPSS job).
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.
- No user action is required.
- 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
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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.