Skip to content
Noroxi
NVD / CVE Program· CNA CERTVDE

CVE-2025-41722: Sauter: Hard-coded Authentication Credentials

Noroxi assessment

Priority: Monitor (action score 30/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.27% (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.
  • Fixed version: Sauter EY-modulo 5 ecos 5 ecos504/505 Firmware v6.0; Sauter EY-modulo 5 modu 5 modu524 Firmware v6.0; Sauter EY-modulo 5 modu 5 modu525 Firmware v6.0.

Low priority for now. Upgrade to Sauter EY-modulo 5 ecos 5 ecos504/505 Firmware v6.0; Sauter EY-modulo 5 modu 5 modu524 Firmware v6.0; Sauter EY-modulo 5 modu 5 modu525 Firmware v6.0 or later.

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 wsc server uses a hard-coded certificate to check the authenticity of SOAP messages. An unauthenticated remote attacker can extract private keys from the Software of the affected devices.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Oct 22, 2025
Updated
Oct 18, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · CERTVDE
7.5
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
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-41722

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for sauter records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

—

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.

  • Sauter EY-modulo 5 ecos 5 ecos504/505

    • 0.0 and later · before Firmware v6.0affected · semver

  • Sauter EY-modulo 5 modu 5 modu524

    • 0.0 and later · before Firmware v6.0affected · semver

  • Sauter EY-modulo 5 modu 5 modu525

    • 0.0 and later · before Firmware v6.0affected · semver

  • Sauter modulo 6 devices modu612-LC

    • 0.0.0 and later · before Firmware v3.2.0affected · semver

  • Sauter modulo 6 devices modu660-AS

    • 0.0.0 and later · before Firmware v3.2.0affected · semver

  • Sauter modulo 6 devices modu680-AS

    • 0.0.0 and later · before Firmware v3.2.0affected · semver

Same product

sauter: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-41723Sauter: Directory Traversal in importFile SOAP Method
    39Monitor
  • CVE-2025-41719Sauter: Improper Validation of user-controlled data
    35Monitor
  • CVE-2025-41724Sauter: Crash via Incomplete SOAP Request
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-41720Oct 22, 2025 · Sauter: Arbitrary File Upload
    17Monitor
  • ← EarlierCVE-2025-41721Oct 22, 2025 · Sauter: Command Injection
    10Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Sauter EY-modulo 5 ecos 5 ecos504/505Firmware v6.0Vendor (CNA)
Sauter EY-modulo 5 modu 5 modu524Firmware v6.0Vendor (CNA)
Sauter EY-modulo 5 modu 5 modu525Firmware v6.0Vendor (CNA)
Sauter modulo 6 devices modu612-LCFirmware v3.2.0Vendor (CNA)
Sauter modulo 6 devices modu660-ASFirmware v3.2.0Vendor (CNA)
Sauter modulo 6 devices modu680-ASFirmware v3.2.0Vendor (CNA)

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.

EPSS, last 120 days

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 researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

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
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-798 · Use of Hard-coded Credentials

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Root cause

For convenience in support or manufacturing, an account that is identical on every device is embedded in the software. Credentials learned from one device work on all of them.

The bug in code

The whole CWE-798 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const SUPPORT_USER = "support";const SUPPORT_PASS = "hardcoded-password";

Fixed

ts
const creds = await provisioning.deviceCredentials(deviceId);if (creds.mustRotate) await forcePasswordChange(deviceId);

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records