What is CVE-2024-6484?A security flaw, explained.
CVE-2024-6484 is a security flaw in the software it affects, published on 11 July 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at under 0.1%. If you run an affected version, plan in the vendor’s fix.
Published 11 July 2024. Record last updated 1 August 2025. We keep this page's data up to date.
What is CVE-2024-6484? In plain terms.
Here is what the published record says about this flaw, and what kind of weakness it is.
Rejected reason: This was not a security issue in Bootstrap. Bootstrap’s JavaScript is not intended to sanitize unsafe or intentionally dangerous HTML. As such, the reported behavior fell outside the scope of Bootstrap’s security model, and the associated CVE has been rescinded.
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
This record has no severity breakdown yet.
Is CVE-2024-6484 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at under 0.1%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2024-6484 scores 0. Action: Track.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2024-6484 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2024-6484? 0 products.
Here is what the published record lists as affected.
No affected products have been listed for this flaw yet. That usually means the record is still being analysed.
How do I fix CVE-2024-6484? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
0 linksNo references have been published for this flaw yet.
Does CVE-2024-6484 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Rejected reason: This was not a security issue in Bootstrap. Bootstrap’s JavaScript is not intended to sanitize unsafe or intentionally dangerous HTML. As su...
- Matched to
- Your software on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2024-6484 is a security flaw in the software it affects, published on 11 July 2024. Here is what the published record says about this flaw, and what kind of weakness it is.
It has no severity score yet. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at under 0.1%. That can change at any time, which is why we keep watching.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.