GCVE-1-2026-0019

Vulnerability from gna-1 – Published: 2026-02-27 14:55 – Updated: 2026-02-27 15:44
VLAI
Title
Improper URL validation in MISP dashboard button widget allows external redirection
Summary
A vulnerability in the dashboard button widget component allows improper handling of user-supplied URLs, which could lead to unintended redirection to external websites. Prior to the fix, the application directly embedded a user-controlled url parameter into an HTML anchor element without validating whether the target was a local path. An attacker able to influence widget configuration could supply a crafted URL containing an external scheme or host, causing users to be redirected to attacker-controlled websites when clicking the dashboard button. The issue results from insufficient validation of URL components before rendering the link. The patch introduces strict parsing and validation using parse_url() to ensure that only relative paths beginning with / are accepted and rejects URLs containing a scheme, host, or user component. If an invalid URL is detected, the application now renders a non-clickable button instead of a link.
CWE
Assigner
CIRCL GNA GNA-1
GNA scorecard A 91/100 over 279 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
misp misp Affected: ≤ 2.5.32
guessed Create a notification for this product.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "misp",
          "vendor": "misp",
          "versions": [
            {
              "lessThanOrEqual": "2.5.32",
              "status": "affected"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Sami Mokaddem"
        },
        {
          "lang": "en",
          "type": "finder",
          "value": "Maxime ESCOURBIAC from Michelin CERT"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eA vulnerability in the dashboard button widget component allows improper handling of user-supplied URLs, which could lead to unintended redirection to external websites.\u003c/p\u003e\n\u003cp\u003ePrior to the fix, the application directly embedded a user-controlled \u003ccode\u003eurl\u003c/code\u003e parameter into an HTML anchor element without validating whether the target was a local path. An attacker able to influence widget configuration could supply a crafted URL containing an external scheme or host, causing users to be redirected to attacker-controlled websites when clicking the dashboard button.\u003c/p\u003e\n\u003cp\u003eThe issue results from insufficient validation of URL components before rendering the link. The patch introduces strict parsing and validation using \u003ccode\u003eparse_url()\u003c/code\u003e to ensure that only relative paths beginning with \u003ccode\u003e/\u003c/code\u003e are accepted and rejects URLs containing a scheme, host, or user component.\u003c/p\u003e\n\u003cp\u003eIf an invalid URL is detected, the application now renders a non-clickable button instead of a link.\u003c/p\u003e\u003cbr\u003e"
            }
          ],
          "value": "A vulnerability in the dashboard button widget component allows improper handling of user-supplied URLs, which could lead to unintended redirection to external websites.\n\n\nPrior to the fix, the application directly embedded a user-controlled url parameter into an HTML anchor element without validating whether the target was a local path. An attacker able to influence widget configuration could supply a crafted URL containing an external scheme or host, causing users to be redirected to attacker-controlled websites when clicking the dashboard button.\n\n\nThe issue results from insufficient validation of URL components before rendering the link. The patch introduces strict parsing and validation using parse_url() to ensure that only relative paths beginning with / are accepted and rejects URLs containing a scheme, host, or user component.\n\n\nIf an invalid URL is detected, the application now renders a non-clickable button instead of a link."
        }
      ],
      "impacts": [
        {
          "descriptions": [
            {
              "lang": "en"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 6.4,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "HIGH",
            "subConfidentialityImpact": "HIGH",
            "subIntegrityImpact": "HIGH",
            "userInteraction": "ACTIVE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "lang": "en"
            }
          ]
        }
      ],
      "providerMetadata": {
        "orgId": "00000000-0000-4000-9000-000000000000"
      },
      "references": [
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/MISP/MISP/commit/f02dafd5086990c6396524ed37ee76d07f23b854"
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Improper URL validation in MISP dashboard button widget allows external redirection",
      "x_gcve": [
        {
          "recordType": "advisory",
          "vulnId": "gcve-1-2026-0019"
        }
      ],
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "00000000-0000-4000-9000-000000000000",
    "datePublished": "2026-02-27T14:55:00.000Z",
    "dateUpdated": "2026-02-27T15:44:29.998063Z",
    "requesterUserId": "00000000-0000-4000-9000-000000000000",
    "serial": 1,
    "state": "PUBLISHED",
    "vulnId": "gcve-1-2026-0019",
    "vulnerabilitylookup_history": [
      [
        "alexandre.dulaunoy@circl.lu",
        "2026-02-27T14:55:29.840231Z"
      ],
      [
        "alexandre.dulaunoy@circl.lu",
        "2026-02-27T15:44:29.998063Z"
      ]
    ]
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.