Mega Fence
Approved changes feed: RSS · Atom
cpe:2.3:a:mega-fence_project:mega-fence:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Mega Fence Project (d75d0324-9d32-534e-948d-ff86e3fcf181) |
|---|---|
| Product | Mega Fence (e64cc0e0-242c-5400-9293-56e093f1d34f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-65328 |
vulnerable | 2026-06-08 07:39:20.842238 |
Details available
Mega-Fence (webgate-lib.*) 25.1.914 and prior trusts the first value of the X-Forwarded-For (XFF) header as the client IP without validating a trusted proxy chain. An attacker can supply an arbitrary XFF value in a remote request to spoof the client IP, which is then propagated to security-relevant state (e.g., WG_CLIENT_IP cookie). Deployments that rely on this value for IP allowlists may be bypassed.
Published: 2026-01-05T00:00:00.000Z
Updated: 2026-01-05T21:08:06.488Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.