dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-13174

MEDIUM · 6.3 CVSS v3.1 Published 2025-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A weakness has been identified in rachelos WeRSS we-mp-rss up to 1.4.7. Affected by this vulnerability is the function do_job of the file /rachelos/we-mp-rss/blob/main/jobs/mps.py of the component Webhook Module. Executing manipulation of the argument web_hook_url can lead to server-side request forgery. The attack may be launched remotely. The exploit has been made available to the public and could be exploited.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the WeRSS we-mp-rss application affecting versions up to 1.4.7. The vulnerability exists in the do_job function within the mps.py file of the Webhook Module, where the web_hook_url parameter is used to construct server-side HTTP requests without proper validation or allowlisting, allowing attackers to manipulate the parameter to make the server request arbitrary URLs.

MitigationImplement strict URL allowlist validation on the web_hook_url parameter to ensure only approved domains/IPs can be used in webhook requests. Additionally, enforce network segmentation and restrict access to internal services and cloud metadata endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WeRSS we-mp-rss is installed
    Look for the we-mp-rss application directory or check installed packages. Common locations include /opt/werss, /var/www/werss, or check via package manager (pip list, npm list, etc.). Also check running web services for we-mp-rss endpoints.
    Affected if WeRSS we-mp-rss application is present on the system
  2. Determine the installed version
    Check the version file, package.json, setup.py, or requirements.txt in the application directory. Look for version 1.4.7 or higher. If no version file exists, check git tags or the application's main entry point for version information.
    Affected if The installed version is 1.4.7 or lower (or version cannot be determined but the application is present)
  3. Locate the Webhook Module
    Search for the mps.py file within the application directory, typically found under a webhook module path such as modules/webhook/mps.py or similar. This file contains the do_job function.
    Affected if The mps.py file exists in the Webhook Module directory
  4. Verify web_hook_url configuration is in use
    Examine the application configuration files (config.yaml, config.json, .env, settings.py) for any web_hook_url, webhook_url, or webhook configuration entries. Check if webhooks are enabled in the module settings.
    Affected if web_hook_url parameter is configured or exposed in the application settings or API endpoints
  5. Check for external input vectors
    Review how the web_hook_url parameter receives input. Look for API endpoints, admin interfaces, or user-accessible forms that accept webhook URLs. Check if these endpoints are accessible without authentication or from untrusted networks.
    Affected if The web_hook_url can be set by external users or untrusted sources, or the webhook configuration interface is exposed to the network

A system is affected if WeRSS we-mp-rss version 1.4.7 or lower is installed, the Webhook Module with mps.py is present, and the web_hook_url parameter is configurable or exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL allowlist validation on the web_hook_url parameter to ensure only approved domains/IPs can be used in webhook requests. Additionally, enforce network segmentation and restrict access to internal services and cloud metadata endpoints.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13174 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data