CVE-2022-31259

Public Exploit

Description

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).

9.8

CVSS

Severity: Critical

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.16%

Third-Party Advisory github.com Third-Party Advisory github.com

Affected: n/a n/a

References

Link	Tags
https://github.com/beego/beego/issues/4946	issue tracking patch exploit third party advisory
https://beego.vip	product
https://github.com/beego/beego/tree/v2.0.2	third party advisory release notes
https://github.com/advisories/GHSA-qx32-f6g6-fcfr

Frequently Asked Questions

What is the severity of CVE-2022-31259?: CVE-2022-31259 has been scored as a critical severity vulnerability.
How to fix CVE-2022-31259?: To fix CVE-2022-31259, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-31259 being actively exploited in the wild?: It is possible that CVE-2022-31259 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.