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

CVE-2026-41195

MEDIUM · 5.0 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/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
mosparo is the modern solution to protect your online forms from spam. Prior to 1.4.13, the automatic rule package source URL feature allows a project member with the editor role to store an attacker-controlled URL that the server later fetches. Because the server follows http/https redirects and does not restrict private or loopback destinations, this becomes a stored SSRF primitive that can be turned into an internal HTTP probing oracle. This vulnerability is fixed in 1.4.13.

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

The automatic rule package source URL feature in mosparo prior to 1.4.13 allows authenticated users with the editor role to store arbitrary URLs that the server subsequently fetches. Because the server follows HTTP/HTTPS redirects without restricting private or loopback destinations, this creates a stored SSRF primitive enabling internal network reconnaissance and service probing.

MitigationUpgrade to mosparo version 1.4.13 which implements proper URL destination validation and restricts following redirects to untrusted/internal addresses.

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
Changed
Confidentiality
Low
Integrity
None
Availability
None

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

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. Determine mosparo installed version
    Locate the version file or check the admin dashboard for the current mosparo version number
    Affected if The installed version is lower than 1.4.13 (e.g., 1.4.12, 1.4.0, etc.)
  2. Verify automatic rule package source URL feature is enabled
    Navigate to Settings > Rule Packages in the mosparo admin interface and check if a rule package source URL is configured under the automatic update section
    Affected if The automatic rule package source URL feature is turned on and pointing to a URL
  3. Identify editor role users
    Check the user management section of mosparo admin for accounts assigned the editor role
    Affected if There are one or more users with editor role permissions who could configure rule package URLs
  4. Inspect configured rule package URLs
    Review all rule package configurations for stored URLs, particularly looking for internal or non-public destinations in the source URL field
    Affected if Any rule package source URLs point to internal network addresses (127.0.0.1, 192.168.x.x, 10.x.x.x, etc.) or private IP ranges
  5. Review server access logs for SSRF indicators
    Examine web server access logs for requests from the mosparo server to internal IP addresses or loopback addresses that were triggered by rule package fetches
    Affected if Logs show HTTP requests from the server to private/loopback addresses originating from rule package URL fetching

You are affected if mosparo version is below 1.4.13 AND the automatic rule package source URL feature is enabled with a configured URL that could be abused for internal network probing.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to mosparo version 1.4.13 which implements proper URL destination validation and restricts following redirects to untrusted/internal addresses.

Recommended fix Moderate confidence

1.4.13

  1. 1. Check the current installed version of mosparo (typically via admin dashboard or command line: bin/console mosparo:version)
  2. 2. Create a complete backup of the mosparo database and configuration files
  3. 3. Upgrade mosparo to version 1.4.13 or later using your installation method (e.g., Composer, Docker, or manual download)
  4. 4. After upgrade, verify the version is 1.4.13 or higher
  5. 5. As an additional hardening measure, consider configuring network restrictions to prevent the web server from making arbitrary outbound HTTP/HTTPS requests to internal/private network ranges (RFC 1918 addresses and loopback addresses)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41195 — 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-2026-41195 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