Skip to content
Noroxi
CVE-2024-6322· NVD / CVE Program· CNA GRAFANA

Access control for plugin data sources protected by the ReqActions json field of the plugin.json is bypassed if the user or service account

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Grafana Grafana 11.1.1, 11.1.3; Grafana Grafana Enterprise 11.1.1, 11.1.3.

Low priority for now. Upgrade to Grafana Grafana 11.1.1, 11.1.3; Grafana Grafana Enterprise 11.1.1, 11.1.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Access control for plugin data sources protected by the ReqActions json field of the plugin.json is bypassed if the user or service account is granted associated access to any other data source, as the ReqActions check was not scoped to each specific datasource. The account must have prior query access to the impacted datasource.

MediumCVSS 5.4 · v3.1—No exploit Fix available
Published
Aug 20, 2024
Updated
Jun 17, 2026
EPSS
0.3% · 21th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GRAFANA
4.4
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-6322

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for grafana records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GRAFANA). Independent of NVD's CPE analysis and usually ahead of it.

  • Grafana Grafana

    • 11.1.0 and later · before 11.1.1affected · semver
    • 11.1.2 and later · before 11.1.3affected · semver

  • Grafana Grafana Enterprise

    • 11.1.0 and later · before 11.1.1affected · semver
    • 11.1.2 and later · before 11.1.3affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/grafana/grafanafrom 0—
Gogithub.com/grafana/grafanafrom 0.0.0-20240521130516-0072e4a92d89 · before 0.0.0-20240725142242-c326d865c58b0.0.0-20240725142242-c326d865c58b
Gogithub.com/grafana/grafanafrom 1.9.2-0.20240521130516-0072e4a92d89 · before 1.9.2-0.20240725142242-c326d865c58b1.9.2-0.20240725142242-c326d865c58b
Gogithub.com/grafana/grafanafrom 11.1.0 · before 11.1.111.1.1
Gogithub.com/grafana/grafanafrom 11.1.2 · before 11.1.311.1.3

Same product

grafana: all records

Other highest-scoring records for the same primary product.

Published before and after this one in the same product

  • ← EarlierCVE-2024-1442Mar 7, 2024 · User with permissions to create a data source can CRUD all data sources
    35Monitor
  • ← EarlierCVE-2024-1313Mar 26, 2024 · Users outside an organization can delete a snapshot with its key
    26Monitor
  • Later →CVE-2024-8118Sep 26, 2024 · Grafana alerting wrong permission on datasource rule write endpoint
    20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Grafana Grafana11.1.1Vendor (CNA)
Grafana Grafana11.1.3Vendor (CNA)
Grafana Grafana Enterprise11.1.1Vendor (CNA)
Grafana Grafana Enterprise11.1.3Vendor (CNA)
Go:github.com/grafana/grafana0.0.0-20240725142242-c326d865c58bPackage registry (OSV)
Go:github.com/grafana/grafana1.9.2-0.20240725142242-c326d865c58bPackage registry (OSV)
Go:github.com/grafana/grafana11.1.1Package registry (OSV)
Go:github.com/grafana/grafana11.1.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
None
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

CWE-266 · Incorrect Privilege Assignment

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records