The route lookup process in beego before 1.12.9 and 2.x before 2.0.3 allows attackers to bypass access control. When a /p1/p2/:name route is configured, attackers can access it by appending .xml in various places (e.g., p1.xml instead of p1).
oryginał ENCVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HBeego
APPBeego≤ 1.12.42.0.0 – 2.0.2
🔵
ZWERYFIKUJ U PRODUCENTA
Brak jednoznacznych danych o patchu. Sprawdź referencje od producenta.
Powiązane podatności
CVE-2025-30223CRITICAL9.3PL ✓ten sam produkt
XSS w funkcji RenderForm() frameworka Beego dla Go
CVE-2022-31836CRITICAL9.8ten sam produkt
The leafInfo.match() function in Beego v2.0.3 and below uses path.join() to deal with wildcardvalues which can...
CVE-2021-30080CRITICAL9.8ten sam produkt
An issue was discovered in the route lookup process in beego before 1.12.11 that allows attackers to bypass ac...
CVE-2024-40465HIGH8.8ten sam produkt
An issue in beego v.2.2.0 and before allows a remote attacker to escalate privileges via the getCacheFileName ...
CVE-2024-40464HIGH8.8ten sam produkt
An issue in beego v.2.2.0 and before allows a remote attacker to escalate privileges via the sendMail function...