Data leak of password hash through change requests

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2023-49280: 0.94% estimated exploitation activity in the next 30 days; percentile 61.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Change request allows to edit any page by default, and the changes are then exported in an XML that anyone can download. So it's possible for an attacker to obtain password hash of users by performing edition of the user profiles and then downloading the XML that has been created. This is also true for any document that might contain password field and that a user can view. This vulnerability impacts all version of Change Request, but the impact depends on the rights that has been set on the wiki since it requires for the user to have the Change request right (allowed by default) and view rights on the page to target. Also the issue cannot be easily exploited in an automated way. Patches The patch consists in denying to users the right of editing pages that contains a password field with change request. It means that already existing change request for those pages won't be removed by the patch, administrators needs to take care of it. The patch is provided in Change Request…

Published by the source

5 Dec 2023, 19:45 UTC

Last modified by the source

5 Dec 2023, 19:45 UTC

Source last checked

26 Oct 2026, 16:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2fr7-cc7p-p45q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-49280

Advisory: Data leak of password hash through change requests
IDs: CVE-2023-49280, GHSA-2fr7-cc7p-p45q
Record: https://patchnext.com/advisories/cve-2023-49280 (revision 1, source checked 26 Oct 2026, 16:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.xwiki.contrib.changerequest:application-changerequest-default 1.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.xwiki.contrib.changerequest:application-changerequest-default: affected >= 0.1, < 1.10; fixed in 1.10

## Suggested inspection (read-only)
- Maven org.xwiki.contrib.changerequest:application-changerequest-default: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.xwiki.contrib.changerequest:application-changerequest-default.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2fr7-cc7p-p45q (GitHub-reviewed advisory GHSA-2fr7-cc7p-p45q lists affected ranges: Maven org.xwiki.contrib.changerequest:application-changerequest-default >=0.1 <1.10)

Commands are suggestions: review each one before running it.