CVE-2024-7096
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 · uneditedA privilege escalation vulnerability exists in multiple WSO2 products due to a business logic flaw in SOAP admin services. A malicious actor can create a new user with elevated permissions only when all of the following conditions are met: * SOAP admin services are accessible to the attacker. * The deployment includes an internally used attribute that is not part of the default WSO2 product configuration. * At least one custom role exists with non-default permissions. * The attacker has knowledge of the custom role and the internal attribute used in the deployment. Exploiting this vulnerability allows malicious actors to assign higher privileges to self-registered users, bypassing intended access control mechanisms.
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 confidenceThis is a business logic vulnerability in WSO2 SOAP admin services where an attacker with knowledge of custom roles and internal deployment attributes can elevate privileges by assigning higher permissions to self-registered users. The flaw allows bypassing access controls when SOAP admin services are exposed and specific configuration conditions exist.
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= 2.0.0= 2.1.0= 2.2.0= 2.5.0= 2.6.0= 3.0.0= 3.1.0= 3.2.0= 3.2.1= 4.0.0= 4.1.0= 4.2.0= 5.2.0= 5.3.0= 5.4.0= 5.4.1= 5.5.0= 5.6.0= 5.7.0= 5.8.0= 5.9.0= 5.10.0= 5.11.0= 6.0.0= 5.3.0= 5.5.0= 5.6.0= 5.7.0= 5.9.0= 5.10.0= 1.3.0= 1.4.0= 1.5.0= 2.0.0= 2.0.0= 1.3.0= 1.4.0= 1.5.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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.
-
Identify WSO2 product and versionCheck the product version by inspecting the product's banner or the <PRODUCT_HOME>/bin/wso2server.bat or wso2server.sh startup script, or look in the carbon.xml file in the repository/conf directoryAffected if The installed product and version match one of the affected versions listed in the CVE advisory (WSO2 API Manager 2.0.0-4.2.0, Identity Server 5.2.0-6.0.0, Identity Server as Key Manager, Open Banking variants)
-
Determine if SOAP admin services are exposed externallyReview network configuration and proxy settings to check whether SOAP admin service endpoints (typically under /services/ or /admin/services/) are reachable from untrusted networks or the public internetAffected if SOAP admin services are accessible from untrusted networks without network-level restrictions
-
Check for custom roles with elevated permissionsReview the user role configuration in the management console or by inspecting the <PRODUCT_HOME>/repository/conf/user-mgt.xml file to identify any non-default custom roles that may grant elevated permissionsAffected if Non-default custom roles exist that could be manipulated by an attacker with knowledge of internal deployment attributes
-
Verify internal deployment attributes are not exposed in user-facing configsExamine the user store and claim configuration files (claim-config.xml, user-mgt.xml) to determine if internal attributes such as internal_roles, internal_permissions, or other deployment-specific attributes are exposed or mappable in user-facing claim mappingsAffected if Internal deployment attributes are exposed in claims that can be read or modified by self-registered users
A user is affected if they run a vulnerable WSO2 product version with SOAP admin services externally accessible and have custom roles or internal attributes exposed in configurations accessible to self-registering users.
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 dataRestrict access to SOAP admin services, review and remove non-default custom roles or permissions, and ensure internal attributes are not exposed in user-facing configurations.
- Consultation8.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 $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7096 — 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-2024-7096 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