CVE-2025-6519
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedE3 Site Supervisor (firmware version < 2.31F01) has a default admin user "ONEDAY" with a daily generated password. An attacker can predictably generate the password for ONEDAY. The oneday user cannot be deleted or modified by any user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe E3 Site Supervisor industrial control system firmware contains a default administrative account 'ONEDAY' with a daily-generated password that follows a predictable algorithm. Attackers can reverse-engineer the password generation mechanism to calculate valid credentials and gain full administrative access. The account cannot be disabled or modified by legitimate administrators, making the vulnerability persistent on affected devices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.31f01CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed firmware versionAccess the device's web interface or check system information via the controller's diagnostic menu. Look for the firmware version displayed in the 'About' or 'System Info' section. Alternatively, check the startup banner or boot logs if you have console access.Affected if The displayed firmware version is below 2.31f01 (or 2.31F01)
-
Verify ONEDAY administrative account existenceAttempt to log into the E3 Site Supervisor web interface or administrative console using the username 'ONEDAY'. The account is present by default on vulnerable firmware versions and cannot be disabled through normal administrative functions.Affected if The ONEDAY account accepts authentication and provides administrative-level access
-
Check if password cannot be modifiedLog in as an administrator (using any valid admin account) and navigate to the user management or account settings section. Attempt to locate, modify, or disable the ONEDAY account through the standard administrative interface.Affected if The ONEDAY account is not visible or cannot be modified/disabled through the administrative panel
-
Assess network exposure of management interfaceDetermine if the E3 Site Supervisor web interface (typically HTTP/HTTPS on ports 80, 443, or custom ports) is reachable from untrusted networks. Review firewall rules and network segmentation configurations around the device.Affected if The device's administrative web interface is accessible from outside the local network or DMZ without proper access controls
A user is affected if their Copeland E3 Supervisory Controller runs firmware version below 2.31f01 and the ONEDAY default account is present and functional on the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.31f01
Upgrade E3 Site Supervisor firmware to version 2.31F01 or later to address the predictable password generation. Implement network segmentation and strict firewall rules to limit exposure to the device's management interfaces until the firmware update can be applied.
2.31F01 or later
- Upgrade E3 Supervisory Controller Firmware to version 2.31F01 or later
- After upgrade, verify the ONEDAY default user has been removed or properly secured
- Confirm the upgrade was successful by checking the firmware version in the system administration panel
- If available, change any default credentials and review user accounts for any unauthorized changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6519 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data