How severe is CVE-2023-49280?

CVE-2023-49280 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Is there a fix for CVE-2023-49280?

Yes. CVE-2023-49280 is fixed in 1.10. Upgrade to this version or later.

Is CVE-2023-49280 exploitable, and should I be worried?

Whether CVE-2023-49280 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-49280 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-49280

Q: What is CVE-2023-49280?

CVE-2023-49280 is a high-severity security vulnerability in org.xwiki.contrib.changerequest:application-changerequest-default (maven), affecting versions >= 0.1, < 1.10. It is fixed in 1.10.

Q: How do I fix CVE-2023-49280?

Upgrade org.xwiki.contrib.changerequest:application-changerequest-default to 1.10 or later.

Summary

Data leak of password hash through change requests

Workarounds

It's possible to workaround the vulnerability by denying manually the Change request right on some spaces, such as XWiki space which will include any user profile by default.

References

JIRA issue: https://jira.xwiki.org/browse/CRAPP-302
- Commit of the fix: https://github.com/xwiki-contrib/application-changerequest/commit/ff0f5368ea04f0e4aa7b33821c707dc68a8c5ca8

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

Thanks Michael Hamann for the report.

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.

CVE-2023-49280 has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.10); upgrading removes the vulnerable code path.

Affected versions

org.xwiki.contrib.changerequest:application-changerequest-default (>= 0.1, < 1.10)

Security releases

org.xwiki.contrib.changerequest:application-changerequest-default → 1.10 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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 1.10, administrators should upgrade immediately.

Frequently Asked Questions

What is CVE-2023-49280? CVE-2023-49280 is a high-severity security vulnerability in org.xwiki.contrib.changerequest:application-changerequest-default (maven), affecting versions >= 0.1, < 1.10. It is fixed in 1.10.
How severe is CVE-2023-49280? CVE-2023-49280 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.xwiki.contrib.changerequest:application-changerequest-default are affected by CVE-2023-49280? org.xwiki.contrib.changerequest:application-changerequest-default (maven) versions >= 0.1, < 1.10 is affected.
Is there a fix for CVE-2023-49280? Yes. CVE-2023-49280 is fixed in 1.10. Upgrade to this version or later.
Is CVE-2023-49280 exploitable, and should I be worried? Whether CVE-2023-49280 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-49280 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-49280? Upgrade org.xwiki.contrib.changerequest:application-changerequest-default to 1.10 or later.