VulnerabilityPublished 14 Nov 2025

CVE-2025-13174: rachelos WeRSS we-mp-rss · Server-Side Request Forgery

Affects rachelos WeRSS we-mp-rssSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% 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/E:P

Base metrics

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

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: 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.
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 14 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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
rachelos WeRSS we-mp-rss	Affected 1.4.0 – 1.4.7 8 affected builds	Fixed in–

AI-suggested

Immediately audit and sanitize all inputs to the web_hook_url parameter to ensure only authorized and validated URLs are accepted.
Implement strict allowlists for outbound HTTP requests from the WeRSS server, restricting connections to trusted endpoints only.
Employ network segmentation and firewall rules to limit server access to internal resources and prevent SSRF exploitation.
Monitor outbound traffic for unusual or unauthorized requests indicative of SSRF attempts.
Apply patches or updates from rachelos as soon as they become available to address this vulnerability.
Consider disabling webhook functionality temporarily if not essential or until secure configurations are verified.
Conduct penetration testing and code reviews focusing on SSRF and input validation weaknesses.
Educate development and operations teams about SSRF risks and secure coding practices related to URL handling.
Use Web Application Firewalls (WAFs) with SSRF detection capabilities to provide an additional layer of defense.
Maintain up-to-date asset inventories to quickly identify and remediate affected WeRSS instances.

Description

CVE-2025-13174 is a medium severity Server-Side Request Forgery (SSRF) vulnerability affecting rachelos WeRSS we-mp-rss versions up to 1.4.7. The flaw exists in the do_job function of the Webhook Module, where manipulation of the web_hook_url argument allows an attacker to induce the server to make unauthorized requests. This vulnerability can be exploited remotely without authentication or user interaction. While no known exploits are currently observed in the wild, public exploit code is available. The CVSS 4.0 score is 5.3, reflecting moderate impact on confidentiality, integrity, and availability with low attack complexity. European organizations using this software, particularly those integrating webhook functionality, could face risks of internal network scanning, data exfiltration, or interaction with internal services.

Impact

For European organizations, exploitation of CVE-2025-13174 could lead to unauthorized internal network access, allowing attackers to scan internal services, access sensitive metadata, or interact with protected APIs. This can result in data leakage, unauthorized command execution, or disruption of critical services. Organizations using WeRSS we-mp-rss in environments with sensitive data or critical infrastructure are at heightened risk. The SSRF can facilitate lateral movement within corporate networks, undermining perimeter defenses. Additionally, attackers could use the vulnerability to bypass firewall rules or access cloud provider metadata services, potentially compromising cloud credentials. The medium severity reflects moderate but tangible risks to confidentiality, integrity, and availability. The absence of required authentication and user interaction lowers the barrier for exploitation, increasing exposure. European entities with webhook integrations in financial, governmental, healthcare, or industrial sectors could face significant operational and reputational damage if exploited.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Nov 2025, 19:07 UTC

Technical details

References

Community reviews

Related threats