Improper Access Control in WSO2 Enterprise Integrator Product via SOAP Admin Services for Logs and User-Store Configuration
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone on the same network segment can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An 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.
- Published
- Oct 16, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-863
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · WSO2
- 5.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | enterprise integrator | cpe:2.3:a:wso2:enterprise_integrator |
| wso2 | enterprise service bus | cpe:2.3:a:wso2:enterprise_service_bus |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 enterprise integrator6.0.0
- wso2 enterprise integrator6.1.0
- wso2 enterprise integrator6.1.1
- wso2 enterprise integrator6.2.0
- wso2 enterprise integrator6.3.0
- wso2 enterprise integrator6.4.0
- wso2 enterprise integrator6.5.0
- wso2 enterprise integrator6.6.0
- wso2 enterprise service bus5.0.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.
WSO2 org.wso2.carbon:org.wso2.carbon.base
- 4.4.8 and later · before 4.4.8.7affected
- 4.4.14 and later · before 4.4.14.5affected
- 4.4.16 and later · before 4.4.16.9affected
- 4.4.26 and later · before 4.4.26.13affected
- 4.4.32 and later · before 4.4.32.16affected
- 4.4.36 and later · before 4.4.36.7affected
- 4.4.40 and later · before 4.4.40.37affected
- 4.5.3 and later · before 4.5.3.45affected
- 4.9 and later · before 4.9.29affected
- 4.10 and later · before 4.10.94affected
WSO2 org.wso2.carbon:org.wso2.carbon.server.admin
- 4.4.8 and later · before 4.4.8.7affected
- 4.4.14 and later · before 4.4.14.5affected
- 4.4.16 and later · before 4.4.16.9affected
- 4.4.26 and later · before 4.4.26.13affected
- 4.4.32 and later · before 4.4.32.16affected
- 4.4.36 and later · before 4.4.36.7affected
- 4.4.40 and later · before 4.4.40.37affected
- 4.5.3 and later · before 4.5.3.45affected
- 4.9 and later · before 4.9.29affected
- 4.10 and later · before 4.10.94affected
WSO2 WSO2 Enterprise Integrator
- before 6.0.0unknown
- 6.0.0 and later · before 6.0.0.22affected
- 6.1.0 and later · before 6.1.0.39affected
- 6.1.1 and later · before 6.1.1.43affected
- 6.2.0 and later · before 6.2.0.62affected
- 6.3.0 and later · before 6.3.0.70affected
- 6.4.0 and later · before 6.4.0.100affected
- 6.5.0 and later · before 6.5.0.107affected
- 6.6.0 and later · before 6.6.0.222affected
WSO2 WSO2 Enterprise Service Bus
- before 5.0.0unknown
- 5.0.0 and later · before 5.0.0.29affected
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-39810An issue was discovered in WSO2 Enterprise Integrator 6.4.0.41Plan
- CVE-2025-1862Authenticated Arbitrary File Upload in Multiple WSO2 Products via BPEL Uploader SOAP Service Leading to Remote Code Execution28Monitor
- CVE-2020-11885WSO2 Enterprise Integrator through 6.6.0 has an XXE vulnerability where a user (with admin console access) can use the XML validator to make28Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-25516Oct 29, 2020 · WSO2 Enterprise Integrator 6.6.0 or earlier contains a stored cross-site scripting (XSS) vulnerability in BPMN explorer tasks.21Monitor
- ← EarlierCVE-2022-39809Sep 9, 2022 · An issue was discovered in WSO2 Enterprise Integrator 6.4.0.24Monitor
- ← EarlierCVE-2024-0392Feb 27, 2025 · Cross-Site Request Forgery (CSRF) in WSO2 Enterprise Integrator 6.6.0 Management Console Due to Missing CSRF Token Validation21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.