Skip to content

← Actionable
Medium, CVSS 6.1

Microweber has Reflected XSS Vulnerability in the layout Parameter

CVE-2025-51502GHSA-mvj3-hc7j-vp74

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Packagist microweber/microweber

    Affected
    >= 2.0.0, <= 2.0.19
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2025-51502: 0.90% estimated exploitation activity in the next 30 days; percentile 59.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Reflected Cross-Site Scripting (XSS) in Microweber CMS 2.0 via the layout parameter on the /admin/page/create page allows arbitrary JavaScript execution in the context of authenticated admin users.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-mvj3-hc7j-vp74

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-51502

Advisory: Microweber has Reflected XSS Vulnerability in the layout Parameter
IDs: CVE-2025-51502, GHSA-mvj3-hc7j-vp74
Record: https://patchnext.com/advisories/cve-2025-51502 (revision 1, source checked 26 Oct 2026, 14:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist microweber/microweber: affected >= 2.0.0, <= 2.0.19

## Suggested inspection (read-only)
- Packagist microweber/microweber: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on microweber/microweber.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mvj3-hc7j-vp74 (GitHub-reviewed advisory GHSA-mvj3-hc7j-vp74 lists affected ranges: Packagist microweber/microweber >=2.0.0 <=2.0.19)

Commands are suggestions: review each one before running it.

Loading voting…