CVE-2025-22956
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 · uneditedOPSI before 4.3 allows any client to retrieve any ProductPropertyState, including those of other clients. This can lead to privilege escalation if any ProductPropertyState contains a secret only intended to be accessible by a subset of clients. One example of this is a domain join account password for the windomain package.
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 confidenceOPSI before version 4.3 contains an Insecure Direct Object Reference (IDOR) vulnerability where client systems can retrieve ProductPropertyState data belonging to any other client without authorization. This allows privilege escalation when sensitive data such as credentials (e.g., domain join passwords for the windomain package) are stored in product property states.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- 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 OPSI versionRun the command 'opsi-admin --version' or check the installed package version via the system package manager (dpkg, rpm, etc.)Affected if The installed version is before 4.3 (e.g., 4.2.x, 4.1.x, etc.)
-
Locate OPSI configuration directoryCommon locations are /etc/opsi or /opt/opsi. Check for opsiconf.conf or main configuration files that indicate the OPSI installationAffected if OPSI is installed and the version cannot be determined or is confirmed below 4.3
-
Verify ProductPropertyState module is in useQuery the OPSI backend database or use ' opsi-productproperty * ' to list ProductPropertyState objects stored in the systemAffected if ProductPropertyState entries exist in the OPSI backend (this indicates the vulnerable feature is active)
-
Check for sensitive data in ProductPropertyStateInspect ProductPropertyState objects for patterns resembling credentials (e.g., password, secret, key, pwd, credential fields) or domain join configurationsAffected if Sensitive data such as passwords, keys, or credentials are stored within ProductPropertyState objects
You are affected if OPSI version is below 4.3 AND ProductPropertyState objects containing sensitive data are present in your environment, as any authenticated client could retrieve them via the IDOR flaw.
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 · scopedUpgrade OPSI to version 4.3 or later to implement proper authorization checks. Additionally, audit and rotate any credentials that may have been exposed through this vulnerability, particularly domain join accounts.
OPSI 4.3
- Upgrade OPSI to version 4.3 or later to resolve the information exposure vulnerability
- After upgrading, verify that client isolation for ProductPropertyState is functioning correctly
- Review any ProductPropertyState values that contain sensitive information (such as domain join credentials) to ensure they are no longer accessible across clients
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22956 — 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-22956 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