CVE-2025-5510VulnerabilityPublished 3 Jun 2025

CVE-2025-5510: quequnlong shiyi-blog · Server-Side Request Forgery

Affects quequnlong shiyi-blogSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 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

Affected software

Product	Affected	Fixed in
GitHubquequnlong/shiyi-blog`pkg:github/quequnlong/shiyi-blog`Other threats	Affected =1.2.0 =1.2.1	Fixed in–

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

AI-suggested

Since no official patches are available, European organizations should implement specific mitigations to reduce risk. First, apply strict input validation and sanitization on the 'url' parameter to ensure only allowed domains or IP ranges can be requested, ideally using a whitelist approach. Implement network-level controls such as egress filtering on the server hosting shiyi-blog to restrict outbound HTTP requests to trusted destinations only. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SSRF payloads targeting the vulnerable endpoint. Monitor logs for unusual outbound requests originating from the application server, especially to internal IP ranges or unexpected external hosts. If possible, isolate the shiyi-blog server in a segmented network zone with limited access to sensitive internal resources. Finally, consider disabling or restricting the functionality of the /app/sys/article/optimize endpoint if it is not critical to business operations until a patch is available.

Description

A vulnerability classified as critical was found in quequnlong shiyi-blog up to 1.2.1. This vulnerability affects unknown code of the file /app/sys/article/optimize. The manipulation of the argument url leads to server-side request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using quequnlong shiyi-blog versions 1.2.0 or 1.2.1, this SSRF vulnerability could lead to unauthorized internal network reconnaissance, data exfiltration, or access to internal services that are otherwise protected. This could compromise confidentiality if sensitive internal APIs or databases are accessible via the SSRF. Integrity and availability impacts are likely limited but could arise if the attacker leverages the SSRF to interact with internal management interfaces or trigger resource exhaustion. Given the medium CVSS score and the lack of authentication requirements, attackers could exploit this vulnerability remotely without user interaction, increasing the risk of automated scanning and exploitation attempts. European organizations with sensitive internal networks or regulatory requirements for data protection (e.g., GDPR) should be concerned about potential data breaches or unauthorized access stemming from this vulnerability. The lack of vendor response and patches increases the window of exposure, necessitating proactive mitigation.

Summary

CVE-2025-5510 is a Server-Side Request Forgery (SSRF) vulnerability identified in the quequnlong shiyi-blog application, specifically affecting versions 1.2.0 and 1.2.1. The vulnerability resides in the /app/sys/article/optimize endpoint, where the 'url' parameter is improperly handled, allowing an attacker to manipulate it to induce the server to make unauthorized requests to internal or external resources. SSRF vulnerabilities enable attackers to abuse the server as a proxy to access internal systems, potentially bypassing firewall restrictions and accessing sensitive information or services not directly exposed to the internet. This vulnerability is remotely exploitable without requiring user interaction or authentication, increasing its risk profile. Although the CVSS 4.0 base score is 5.3 (medium severity), the impact can vary depending on the internal network configuration and the sensitivity of accessible resources. The vendor has not responded to disclosure attempts, and no patches or mitigations have been published yet. There are no known exploits in the wild at this time, but public disclosure means attackers could develop exploits. The vulnerability's vector metrics indicate low attack complexity and no privileges or user interaction required, but the impact on confidentiality, integrity, and availability is limited to low, suggesting that while the server can be used to make requests, the direct damage potential is somewhat constrained by the application context or additional controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 06:20 UTC

Technical details

References

Community reviews

Related threats