How severe is GHSA-gwj6-xpfg-pxwr?

No CVSS score has been assigned to GHSA-gwj6-xpfg-pxwr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gwj6-xpfg-pxwr?

GHSA-gwj6-xpfg-pxwr affects the following packages: org.xwiki.contrib.blog:application-blog-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gwj6-xpfg-pxwr?

Update org.xwiki.contrib.blog:application-blog-ui to 9.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gwj6-xpfg-pxwr is resolved across your whole dependency graph.

How do I detect GHSA-gwj6-xpfg-pxwr in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.contrib.blog:application-blog-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gwj6-xpfg-pxwr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-gwj6-xpfg-pxwr actively exploited in the wild?

No public exploit code has been indexed for GHSA-gwj6-xpfg-pxwr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gwj6-xpfg-pxwr?

GHSA-gwj6-xpfg-pxwr has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gwj6-xpfg-pxwr?

GHSA-gwj6-xpfg-pxwr is classified as CWE-95 (CWE-95). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gwj6-xpfg-pxwr published, and has it been updated?

GHSA-gwj6-xpfg-pxwr was published on September 8, 2025 and was last updated on September 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

XWiki Blog Application: Privilege Escalation (PR) from account through blog contentGHSA-gwj6-xpfg-pxwr

Fix: xwiki-contrib/application-blog@b98ab6f

GHSA-gwj6-xpfg-pxwr is a CWE-95 vulnerability in org.xwiki.contrib.blog:application-blog-ui. A fix is available for org.xwiki.contrib.blog:application-blog-ui — see the affected versions and patch details below.

Also known asCVE-2025-58365

Published

Sep 8, 2025

Updated

Sep 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-gwj6-xpfg-pxwr.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.xwiki.contrib.blog:application-blog-ui

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.contrib.blog:application-blog-ui`	all versions	9.14`org.xwiki.contrib.blog:application-blog-ui:9.14`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.contrib.blog:application-blog-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.contrib.blog:application-blog-ui to 9.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gwj6-xpfg-pxwr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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. ### R

O3 Security · Impact-Aware SCA

Is GHSA-gwj6-xpfg-pxwr in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works