How severe is GHSA-28r6-jm5h-mrgg?

No CVSS score has been assigned to GHSA-28r6-jm5h-mrgg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-28r6-jm5h-mrgg?

GHSA-28r6-jm5h-mrgg affects the following packages: github.com/beego/beego/v2 (Go), github.com/beego/beego (Go). Ecosystems affected: Go.

How do I fix GHSA-28r6-jm5h-mrgg?

Update github.com/beego/beego/v2 to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-28r6-jm5h-mrgg is resolved across your whole dependency graph.

How do I detect GHSA-28r6-jm5h-mrgg in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/beego/beego/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-28r6-jm5h-mrgg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-28r6-jm5h-mrgg?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-28r6-jm5h-mrgg can be triaged on real exposure rather than presence alone.

Is GHSA-28r6-jm5h-mrgg actively exploited in the wild?

No public exploit code has been indexed for GHSA-28r6-jm5h-mrgg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-28r6-jm5h-mrgg?

GHSA-28r6-jm5h-mrgg has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-28r6-jm5h-mrgg published, and has it been updated?

GHSA-28r6-jm5h-mrgg was published on April 6, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-28r6-jm5h-mrgg — v2

Fix: beego/beego#4459

GHSA-28r6-jm5h-mrgg is a security vulnerability in github.com/beego/beego/v2. A fix is available for github.com/beego/beego/v2 — see the affected versions and patch details below.

Access control bypass in Beego

Also known asCVE-2021-30080GO-2022-0572

Published

Apr 6, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐹github.com/beego/beego/v2🐹github.com/beego/beego

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in the route lookup process in beego before 1.12.11 that allows attackers to bypass access control.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/beego/beego/v2`	≥ 2.0.0&&< 2.0.3	2.0.3`go get github.com/beego/beego/v2@v2.0.3`
🐹Go	`github.com/beego/beego`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/beego/beego/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/beego/beego/v2 to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-28r6-jm5h-mrgg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-28r6-jm5h-mrgg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-28r6-jm5h-mrgg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in the route lookup process in beego through 2.0.1, allows attackers to bypass access control.

O3 Security · Impact-Aware SCA

Is GHSA-28r6-jm5h-mrgg in your dependencies?

O3 Security finds GHSA-28r6-jm5h-mrgg across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works