CVE-2022-41555
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 · uneditedThe affected product DIAEnergie (versions prior to v1.9.01.002) is vulnerable to a stored cross-site scripting vulnerability through the PutLineMessageSetting API.
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 · moderate confidenceDIAEnergie versions prior to v1.9.01.002 contain a stored cross-site scripting (XSS) vulnerability in the PutLineMessageSetting API. The API fails to properly sanitize user input, allowing attackers to inject malicious JavaScript that persists on the server and executes in the browsers of other users who access the affected functionality.
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< 1.9.01.002CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Locate DIAEnergie installationSearch for DIAEnergie directories on the system, typically found in C:\Program Files\Deltaww or C:\inetpub\wwwroot\DIAEnergie. Check for files named DiaEnergie.exe, EnergieShell.dll, or configuration files containing 'DIAEnergie' in their path.Affected if DIAEnergie software is present on the system
-
Identify installed DIAEnergie versionCheck the version of the main DIAEnergie assembly or executable. Right-click on the main DLL/EXE file, select Properties, then look at the Details tab for Product Version. Alternatively, check version info in the application's bin directory or read any version.txt/readme.txt files included with the installation.Affected if Installed version is earlier than 1.9.01.002 (e.g., 1.9.00.001, 1.8.x, etc.)
-
Verify PutLineMessageSetting API accessibilityReview web.config or application configuration files for the PutLineMessageSetting API endpoint. Check if the API is exposed through IIS or the application's routing configuration.Affected if The PutLineMessageSetting API endpoint is accessible and enabled in the application configuration
-
Inspect application logs for suspicious inputSearch DIAEnergie application logs (typically in Logs folder within the installation directory) for any entries containing JavaScript tags, script elements, or unusual characters that may indicate XSS payload storage.Affected if Logs contain suspicious script-like content in message settings or user input fields that suggest exploitation
A system is affected if DIAEnergie is installed with a version earlier than 1.9.01.002 and the PutLineMessageSetting API is accessible.
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 · scoped1.9.01.002
Upgrade DIAEnergie to version v1.9.01.002 or later. Until the upgrade is applied, implement output encoding and input validation on the PutLineMessageSetting API endpoint and restrict access to trusted users only.
1.9.01.002
- Upgrade DIAEnergie to version 1.9.01.002 or later to remediate the stored XSS vulnerability in the PutLineMessageSetting API
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41555 — 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-2022-41555 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