VRT Sign in

Flamingo CVEs with no public exploit

1 CVE

Look up CVE IDs Status Exploitation Severity

Reset

Overview 1 match · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC

1match 0protected0.0% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0%

Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 100.0%

Critical 1 100.0% High 0 0.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%

blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 1 100.0% not established 0 0.0% unrecorded 0 0.0%

Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 1 100.0% No public exploit 0 0.0%

split by StatusSeverityProtectionExploit maturity peak 1 / month

Mar 231 No exploit published1 Critical1 not blocked1 Forecast only1

Mar 23

1 match Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.

CVE	Severity	Published▾	Status	Exploitation	Description
CVE-2023-26477	Critical	2023-03-02	No exploit published	Forecast only	XWiki Platform is a generic wiki platform. Starting in versions 6.3-rc-1 and 6.2.4, it's possible to inject arbitrary wiki syntax including Groovy, Python and Velocity script macros via the `newThemeName` request parameter (URL parameter), in combination with additional parameters. This has been patched in the supported versions 13.10.10, 14.9-rc-1, and 14.4.6. As a workaround, it is possible to edit `FlamingoThemesCode.WebHomeSheet` and manually perform the changes from the patch fixing the issue.

CVE

Severity

Published▾

Status

Exploitation

Description

CVE-2023-26477

Critical

2023-03-02

No exploit published

Forecast only

XWiki Platform is a generic wiki platform. Starting in versions 6.3-rc-1 and 6.2.4, it's possible to inject arbitrary wiki syntax including Groovy, Python and Velocity script macros via the `newThemeName` request parameter (URL parameter), in combination with additional parameters. This has been patched in the supported versions 13.10.10, 14.9-rc-1, and 14.4.6. As a workaround, it is possible to edit `FlamingoThemesCode.WebHomeSheet` and manually perform the changes from the patch fixing the issue.