CVE-2025-48885VulnerabilityPublished 30 May 2025

CVE-2025-48885: xwikisas application-urlshortener · Cross-Site Request Forgery (CSRF)

Affects xwikisas application-urlshortenerSource CVE Database V5

Not known to be exploited · CVSS 5.7 Medium : upgrade to 1.2.4 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.2.4

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade xwikisas/application-urlshortener to 1.2.4.

Affected software

Product	Affected	Fixed in
GitHubxwikisas/application-urlshortener`pkg:github/xwikisas/application-urlshortener`Other threats	Affected <1.2.4	Fixed in 1.2.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade the application-urlshortener component to version 1.2.4 or later, where the CSRF vulnerability is fixed. Since no workarounds are available, patching is critical. Organizations should also implement the following measures: 1) Enforce strict access controls on the wiki, limiting view access to trusted users where possible to reduce exposure. 2) Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious POST requests that attempt mass page creation or unusual URL patterns. 3) Monitor wiki page creation logs for anomalous spikes in page creation activity, enabling rapid detection and response to abuse. 4) Educate administrators on the importance of timely updates and monitoring for unusual wiki behavior. 5) Consider implementing additional CSRF protections at the application or proxy level if feasible, such as validating origin headers or requiring tokens for state-changing requests. These steps, combined with patching, will reduce the risk and impact of exploitation.

Description

application-urlshortener create shortened URLs for XWiki pages. Versions prior to 1.2.4 are vulnerable to users with view access being able to create arbitrary pages. Any user (even guests) can create these docs, even if they don't exist already. This can enable guest users to denature the structure of wiki pages, by creating 1000's of pages with random name, that then become very difficult to handle by admins. Version 1.2.4 fixes the issue. No known workarounds are available.

Impact

For European organizations using xwikisas with the vulnerable application-urlshortener versions, this vulnerability can lead to significant operational disruption. Unauthorized creation of thousands of wiki pages can clutter and corrupt the wiki's content structure, impeding knowledge management and collaboration workflows. This can degrade productivity, increase administrative overhead, and potentially cause confusion or misinformation if malicious or misleading pages are introduced. While confidentiality and availability impacts are limited, the integrity of the wiki content is severely affected. Organizations relying on XWiki for internal documentation, project management, or compliance records may face compliance risks if data integrity cannot be assured. Additionally, the ability for unauthenticated guests to perform these actions increases the attack surface, making public-facing wikis particularly vulnerable to abuse or vandalism. Although no direct data exfiltration or system compromise is indicated, the operational impact and potential reputational damage from defaced or corrupted content are notable concerns.

Summary

CVE-2025-48885 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the application-urlshortener component of the xwikisas platform, specifically versions prior to 1.2.4. The application-urlshortener is designed to create shortened URLs for XWiki pages. Due to insufficient CSRF protections, users with view access—including unauthenticated guest users—can exploit this flaw to create arbitrary wiki pages without proper authorization. This means that even guests can generate thousands of pages with random names, overwhelming the wiki structure and making administrative management difficult or impractical. The vulnerability arises because the application does not properly verify the origin or intent of requests to create pages, allowing attackers to craft malicious requests that execute unintended actions on behalf of legitimate users. The issue was addressed in version 1.2.4, and no known workarounds exist, emphasizing the importance of timely patching. The CVSS v4.0 score is 5.7 (medium severity), reflecting the network attack vector, low attack complexity, no privileges required, no user interaction, but with a high impact on integrity due to unauthorized page creation. There are no known exploits in the wild at this time.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 13:55 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats