XWiki Blog Application: Privilege Escalation (PR) from account through blog content

Exploitation

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

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-58365: 0.58% estimated exploitation activity in the next 30 days; percentile 47.98 (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 The blog application in XWiki allowed remote code execution for any user who has edit right on any page. Normally, these are all logged-in users as they can edit their own user profile. To exploit, it is sufficient to add an object of type Blog.BlogPostClass to any page and to add some script macro with the exploit code to the "Content" field of that object. Patches The vulnerability has been patched in the blog application version 9.14 by executing the content of blog posts with the rights of the appropriate author. Workarounds We're not aware of any workarounds. Resources https://jira.xwiki.org/browse/BLOG-191 https://github.com/xwiki-contrib/application-blog/commit/b98ab6f17da3029576f42d12b4442cd555c7e0b4

Published by the source

8 Sep 2025, 20:59 UTC

Last modified by the source

10 Sep 2025, 21:05 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gwj6-xpfg-pxwr

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

# Patch Next advisory brief: CVE-2025-58365

Advisory: XWiki Blog Application: Privilege Escalation (PR) from account through blog content
IDs: CVE-2025-58365, GHSA-gwj6-xpfg-pxwr
Record: https://patchnext.com/advisories/cve-2025-58365 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.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.blog:application-blog-ui 9.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.xwiki.contrib.blog:application-blog-ui: affected < 9.14; fixed in 9.14

## Suggested inspection (read-only)
- Maven org.xwiki.contrib.blog:application-blog-ui: 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.blog:application-blog-ui.
- 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-gwj6-xpfg-pxwr (GitHub-reviewed advisory GHSA-gwj6-xpfg-pxwr lists affected ranges: Maven org.xwiki.contrib.blog:application-blog-ui >=0 <9.14)

Commands are suggestions: review each one before running it.