Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13814: Server-Side Request Forgery in moxi159753 Mogu Blog v2

0
Medium
VulnerabilityCVE-2025-13814cvecve-2025-13814
Published: Mon Dec 01 2025 (12/01/2025, 07:32:06 UTC)
Source: CVE Database V5
Vendor/Project: moxi159753
Product: Mogu Blog v2

Description

A security flaw has been discovered in moxi159753 Mogu Blog v2 up to 5.2. Impacted is the function LocalFileServiceImpl.uploadPictureByUrl of the file /file/uploadPicsByUrl. The manipulation results in server-side request forgery. The attack can be launched remotely. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 12/01/2025, 07:55:22 UTC

Technical Analysis

CVE-2025-13814 is a server-side request forgery (SSRF) vulnerability affecting moxi159753 Mogu Blog v2 up to version 5.2. The vulnerability resides in the LocalFileServiceImpl.uploadPictureByUrl function, which processes requests to the /file/uploadPicsByUrl endpoint. This function allows an attacker to supply a URL parameter that the server fetches to upload pictures. Due to insufficient validation or filtering of the supplied URL, an attacker can coerce the server into making arbitrary HTTP requests to internal or external systems. This can be exploited remotely without authentication or user interaction, increasing the attack surface. The SSRF can be leveraged to access internal services, bypass firewalls, or perform reconnaissance within the victim’s network. The vulnerability has a CVSS 4.0 base score of 6.9, reflecting medium severity with network attack vector, low complexity, and no privileges or user interaction required. The vendor was contacted but did not respond or provide a patch, and a public exploit has been released, increasing the urgency for mitigation. No official patches or updates are currently available, leaving systems exposed. This vulnerability is particularly concerning for organizations that expose Mogu Blog v2 instances to the internet or use it in environments with sensitive internal services accessible from the blog server.

Potential Impact

For European organizations, exploitation of this SSRF vulnerability could lead to unauthorized internal network access, allowing attackers to scan internal IP ranges, access metadata services, or interact with internal APIs not intended for public access. This could result in data leakage, unauthorized access to sensitive information, or pivoting to further compromise internal systems. The ability to launch the attack remotely without authentication increases the risk of widespread exploitation, especially for publicly accessible Mogu Blog v2 installations. Organizations in sectors such as government, finance, healthcare, and critical infrastructure that rely on Mogu Blog v2 for content management or communication may face increased risks of espionage, data breaches, or service disruption. The lack of vendor response and patch availability further exacerbates the threat, requiring organizations to implement compensating controls promptly. Additionally, the public availability of an exploit increases the likelihood of opportunistic attacks targeting vulnerable European entities.

Mitigation Recommendations

European organizations should immediately audit their environments to identify any instances of Mogu Blog v2 versions 5.0 through 5.2. Since no official patch is available, organizations should implement strict input validation and filtering on the uploadPicsByUrl endpoint to restrict URLs to trusted domains or disable the feature entirely if not required. Network-level controls such as egress filtering and firewall rules should be applied to prevent the blog server from making arbitrary outbound requests, especially to internal IP ranges or sensitive services. Deploying web application firewalls (WAFs) with custom rules to detect and block SSRF patterns targeting the vulnerable endpoint can provide additional protection. Monitoring and logging outbound HTTP requests from the blog server can help detect exploitation attempts. Organizations should also consider isolating the blog server in a segmented network zone with minimal access to internal resources. Finally, maintain vigilance for updates from the vendor or community patches and plan for timely application once available.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-11-30T19:51:24.060Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 692d458c0729cca2074a0c73

Added to database: 12/1/2025, 7:36:44 AM

Last enriched: 12/1/2025, 7:55:22 AM

Last updated: 12/4/2025, 12:15:37 PM

Views: 18

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats