CVE-2025-9955
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 · uneditedAn improper access control vulnerability exists in WSO2 Enterprise Integrator product due to insufficient permission restrictions on internal SOAP admin services related to system logs and user-store configuration. A low-privileged user can access log data and user-store configuration details that are not intended to be exposed at that privilege level. While no credentials or sensitive user information are exposed, this vulnerability may allow unauthorized visibility into internal operational details, which could aid in further exploitation or reconnaissance.
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 confidenceImproper access control in WSO2 Enterprise Integrator allows low-privileged users to access internal SOAP admin services related to system logs and user-store configuration. The vulnerability stems from insufficient permission restrictions that should prevent unauthenticated or low-privileged access to these administrative functions.
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= 6.0.0= 6.1.0= 6.1.1= 6.2.0= 6.3.0= 6.4.0= 6.5.0= 6.6.0= 5.0.0CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify WSO2 product versionLocate the product version by checking the product.xml file in the installation directory, or look for a version file in the WSO2 installation root folder. Alternatively, access the WSO2 Carbon management console and check the 'About' section under 'System' or 'Manage' menu.Affected if The installed version matches any of the following: WSO2 Enterprise Integrator 6.0.0, 6.1.0, 6.1.1, 6.2.0, 6.3.0, 6.4.0, 6.5.0, 6.6.0, or WSO2 Enterprise Service Bus 5.0.0
-
Verify access to system log SOAP admin servicesAttempt to access or invoke the internal SOAP admin service related to system logs. This is typically found at an endpoint such as /services/LogViewer or similar log administration service under the WSO2 services directory. Use an unauthenticated or low-privileged test account to attempt access.Affected if The SOAP admin service for system logs responds without proper authorization or returns administrative log data to a low-privileged or unauthenticated user.
-
Verify access to user-store configuration SOAP admin servicesAttempt to access or invoke the internal SOAP admin service related to user-store configuration. This is typically found at an endpoint such as /services/UserStoreManager or similar user management service under the WSO2 services directory. Use an unauthenticated or low-privileged test account to attempt access.Affected if The SOAP admin service for user-store configuration responds without proper authorization or returns user store configuration data to a low-privileged or unauthenticated user.
-
Confirm service is using standard WSO2 admin service pathsReview the WSO2 server configuration and access logs to confirm that internal SOAP admin services are exposed on standard paths such as /services/ without additional authorization filters applied.Affected if Internal SOAP admin services are accessible at standard WSO2 service endpoints without explicit authorization restrictions in place.
You are affected if your environment runs a matching version AND low-privileged or unauthenticated users can access internal SOAP admin services for system logs or user-store configuration.
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.
From vendor dataApply proper authorization checks to internal SOAP admin services to restrict access to system logs and user-store configuration to only authorized administrative users, or apply vendor-supplied patches/security updates addressing this access control flaw.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9955 — 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-9955 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