LaraDashboard before 1.4.9 Stored XSS via LaraBuilder design_json Block Content
LaraDashboard versions before 1.4.9, including v1.4.2, are affected when LaraBuilder text-editor or html blocks render unsanitized content. Fixed in 1.4.9.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.9
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. LaraDashboard version v1.4.2 is affected Attacker has post.create permission to store builder blocks Payload is in a LaraBuilder text-editor or html block rendered without sanitization
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.4.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
LaraDashboard before 1.4.9 contains a stored cross-site scripting vulnerability that allows authenticated users with post.create or post.edit permission to inject scripts via unsanitized LaraBuilder design_json block content. Attackers can save text-editor, HTML, text or heading blocks containing script or event-handler markup that executes in administrator or Superadmin sessions viewing the builder, preview or page.
What to do
Check whether your setup matches what the bug needs.
LaraDashboard version v1.4.2 is affected Attacker has post.create permission to store builder blocks Payload is in a LaraBuilder text-editor or html block rendered without sanitizationUpgrade to a fixed version: 1.4.9.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- LaraDashboard LaraDashboard
fixed in 1.4.9
Evidence 7
- Advisory
- Advisory
- Advisory
- Patch
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120488
What does this mean?
LaraBuilder text-editor and html blocks render stored HTML and JavaScript without sanitization, so a script planted in a block runs when an administrator or editor opens the builder preview or page. The script then acts with that user's privileges.Source: github.com
Am I affected, and how do I check?
The affected range runs from the start up to but not including 1.4.9, and the advisory lists v1.4.2 as affected. The setup involves LaraBuilder text-editor or html blocks and users with post.create, which includes authors, editors, and members allowed by the membership module. To check the version, look at the LaraDashboard version in the installation.Source: github.com
What should I do about it?
Upgrade LaraDashboard to version 1.4.9 or later.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data