dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-41651

MEDIUM · 5.4 CVSS v3.1 Published 2022-10-27
Fix available
A fix is available. Upgrade to 1.9.01.002 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The affected product DIAEnergie (versions prior to v1.9.01.002) is vulnerable to a stored cross-site scripting vulnerability through the SetPF 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 · high confidence

DIAEnergie versions prior to v1.9.01.002 contain a stored cross-site scripting vulnerability in the SetPF API endpoint. User-supplied input is not properly sanitized, allowing malicious JavaScript code to be persistently stored and executed when other users access the affected functionality.

MitigationUpgrade DIAEnergie to v1.9.01.002 or later. If upgrading is not immediately feasible, implement input validation and output encoding on the SetPF API to neutralize malicious script content.

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
DiaenergieApplication
Affected:< 1.9.01.002

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate DIAEnergie installation and identify version
    Check system for DIAEnergie installation directories or application listings, then look for version information typically found in about pages, readme files, or application metadata within the installation folder.
    Affected if The installed version is prior to 1.9.01.002
  2. Compare installed version to affected range
    If version information is found, compare it against the vulnerable range: any version less than 1.9.01.002 is affected.
    Affected if The installed version is < 1.9.01.002
  3. Verify SetPF API endpoint exists and is accessible
    Identify if the web application exposes the SetPF API endpoint. This is typically a web service endpoint within the DIAEnergie application accessible via HTTP/HTTPS.
    Affected if The SetPF API endpoint is present and accessible in the environment
  4. Check if user input handling on SetPF lacks sanitization
    Inspect the SetPF API functionality to determine whether user-supplied input is being stored and rendered without proper input validation or output encoding.
    Affected if The SetPF endpoint stores and displays user input without sanitization, allowing script execution

A system is affected if DIAEnergie version is below 1.9.01.002 and the SetPF API endpoint is accessible and processes user input without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.9.01.002 or later
Fixed in 1.9.01.002
Interim mitigation

Upgrade DIAEnergie to v1.9.01.002 or later. If upgrading is not immediately feasible, implement input validation and output encoding on the SetPF API to neutralize malicious script content.

Recommended fix High confidence

DIAEnergie v1.9.01.002

  1. Identify the current version of DIAEnergie installed in your environment
  2. Contact Diaenergie vendor to obtain the v1.9.01.002 or later release that contains the fix for the stored XSS vulnerability
  3. Review any vendor release notes or documentation for the update
  4. Apply the update to all affected DIAEnergie instances following vendor-provided installation instructions
  5. After updating, verify that the SetPF API no longer accepts malicious script payloads
  6. Confirm the fix by testing that user-supplied input through SetPF is properly sanitized or encoded

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Diaenergie Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41651 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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