GHSA-f963-4cq8-2gw7 CVE-2024-43401
In XWiki Platform, payloads stored in content is executed when a user with script/programming right edit them
High
Maven
- Severity
- 0.0 / 10
- High · CVSS 4.0
- Exploit chance (EPSS)
- 0.68%
- Chance of exploitation in the next 30 days. Higher than 52.32% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
15.10-rc-1- Upgrade org.xwiki.platform:xwiki-platform-web-templates to this version or later
Description
Impact
A user without script/programming right can trick a user with elevated rights to edit a content with a malicious payload using a WYSIWYG editor. The user with elevated rights is not warned beforehand that they are going to edit possibly dangerous content. The payload is executed at edit time.
Patches
This vulnerability has been patched in XWiki 15.10RC1.
Workarounds
No workaround. It is advised to upgrade to XWiki 15.10+.
References
- https://jira.xwiki.org/browse/XWIKI-20331
- https://jira.xwiki.org/browse/XWIKI-21311
- https://jira.xwiki.org/browse/XWIKI-21481
- https://jira.xwiki.org/browse/XWIKI-21482
- https://jira.xwiki.org/browse/XWIKI-21483
- https://jira.xwiki.org/browse/XWIKI-21484
- https://jira.xwiki.org/browse/XWIKI-21485
- https://jira.xwiki.org/browse/XWIKI-21486
- https://jira.xwiki.org/browse/XWIKI-21487
- https://jira.xwiki.org/browse/XWIKI-21488
- https://jira.xwiki.org/browse/XWIKI-21489
- https://jira.xwiki.org/browse/XWIKI-21490
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Attribution
This vulnerability has been reported on Intigriti by @floerer
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.xwiki.platform:xwiki-platform-web-templates | < 15.10-rc-1 |
15.10-rc-1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.xwiki.platform:xwiki-platform-web-templates Maven → 15.10-rc-1
- maven
<dependency><groupId>org.xwiki.platform</groupId><artifactId>xwiki-platform-web-templates</artifactId><version>15.10-rc-1</version></dependency>- gradle
implementation("org.xwiki.platform:xwiki-platform-web-templates:15.10-rc-1")
Severity breakdown
CVSS 4.0 0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- Low
- User interaction
- Passive
- Confidentiality (vulnerable system)
- High
- Integrity (vulnerable system)
- High
- Availability (vulnerable system)
- High
- Confidentiality (subsequent systems)
- High
- Integrity (subsequent systems)
- High
- Availability (subsequent systems)
- High
CVSS 3.1 9.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-269: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system.
- Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
CWE-862: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How to prevent it
- Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
References
Advisories
Packages
Other links
- github.com/xwiki/xwiki-platform/security/advisories/GHSA-f963-4cq8-2gw7
- jira.xwiki.org/browse/XWIKI-20331
- jira.xwiki.org/browse/XWIKI-21311
- jira.xwiki.org/browse/XWIKI-21481
- jira.xwiki.org/browse/XWIKI-21482
- jira.xwiki.org/browse/XWIKI-21483
- jira.xwiki.org/browse/XWIKI-21484
- jira.xwiki.org/browse/XWIKI-21485
- jira.xwiki.org/browse/XWIKI-21486
- jira.xwiki.org/browse/XWIKI-21487
- jira.xwiki.org/browse/XWIKI-21488
- jira.xwiki.org/browse/XWIKI-21489
- jira.xwiki.org/browse/XWIKI-21490
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-w4fj-87j5-f25c XWiki has Reflected Cross-Site Scripting (XSS) in page history compare | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-wvqx-m5px-6cmp XWiki Affected by Reflected Cross-Site Scripting (XSS) in Error Messages | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-7vpr-jm38-wr7w XWiki vulnerable to a reflected XSS via xredirect parameter in DeleteApplication | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-m9x4-w7p9-mxhx XWiki allows Reflected XSS in two templates | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-692v-783f-mg8x XWiki Platform vulnerable to Cross-Site Scripting (XSS) through conflict resolution | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-93gh-jgjj-r929 XWiki Platform vulnerable to XSS with edit right in the create document form for existing pages | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-qcj9-gcpg-4w2w XWiki Platform web templates vulnerable to reflected XSS in the create document form if name validation is enabled | Critical | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-ghf6-2f42-mjh9 XWiki users can be tricked to execute scripts as the create page action doesn't display the page's title | High | Also affects org.xwiki.platform:xwiki-platform-web-templates |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor