GHSA-M8XX-3X29-84H8
Vulnerability from github – Published: 2026-06-03 20:25 – Updated: 2026-06-03 20:29Impact
It’s a “moderate” vulnerability… but being an admin panel, we take this seriously. It’s difficult… but an attacker could conduct a targeted phishing campaign, in order to trick your users or admins to click a malicious link, which under very specific circumstances could give them information... or even admin access. It’s unlikely, but that’s not good enough in admin panels - we should make it impossible. That’s why we’re bothering you with this.
Patches
If you don’t have custom error views, the views provided by Backpack would output the exception message without escaping it, which made an attack possible using Reflected XSS, in some very specific circumstances (that we will not disclose). To fix those error views in Backpack 4.x and 5.x, please run:
composer update backpack/crud
php artisan backpack:fix
The problem has been patched in: - v4.0.63 - v4.1.69 - v5.0.13
IMPORTANT! Running a
composer updateshould get you the patched version, but you also need to runphp artisan backpack:fixafterwards, to patch your published error views, if necessary.
Workarounds
Alternatively (if you don’t want to run composer update), you can manually look inside your error views in “resources/views/errors” and output e($exception->getMessage()) instead of $exception->getMessage(). That’s all there is to the fix, really.
What the maintainers have done about this
Acted as soon as our team found it (last week of March 2022):
- Pushed patches to 5.x, 4.1 and 4.0;
- Made it easy to apply the fix to existing projects, using a new php artisan backpack:fix command;
- Kept the specific circumstances a secret; as far as we know, only our team knows about the niche case where this exploit is possible;
- Emailed all our licensed users, to have a chance to fix their projects before it’s public;
- Sent an email blast to our 25.000+ strong Security Newsletter;
- Made this public with a blog post and soon a CVE, after our community has had a reasonable chance to fix their projects;
- Will continue to monitor this and remind paying users to apply this fix if they haven’t;
For more information
If you have any questions or comments about this advisory: * Open an issue in backpack/crud * Email us at hello@backpackforlaravel.com
PS. You can read this blog post for more information.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "backpack/crud"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.0.13"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "backpack/crud"
},
"ranges": [
{
"events": [
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.69"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "backpack/crud"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.0.63"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-31114"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-03T20:25:50Z",
"nvd_published_at": "2026-06-03T16:16:18Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nIt\u2019s a \u201c*moderate*\u201d vulnerability\u2026 but being an admin panel, we take this seriously. It\u2019s difficult\u2026 but an attacker could conduct a targeted phishing campaign, in order to **trick your users or admins to click a malicious link, which under very specific circumstances could give them information... or even admin access**. It\u2019s *unlikely*, but that\u2019s not good enough in admin panels - we should make it *impossible*. That\u2019s why we\u2019re bothering you with this. \n\n### Patches\n\n\nIf you don\u2019t have custom error views, the views provided by Backpack would output the exception message *without escaping it*, which made an attack possible using Reflected XSS, in some very specific circumstances (that we will not disclose). **To fix those error views in Backpack 4.x and 5.x, please run**:\n\n```bash\ncomposer update backpack/crud\nphp artisan backpack:fix\n```\n\nThe problem has been patched in:\n- v4.0.63\n- v4.1.69\n- v5.0.13\n\n\u003e **IMPORTANT! Running a `composer update` should get you the patched version, but you also need to run `php artisan backpack:fix` afterwards, to patch your published error views, if necessary.**\n\n### Workarounds\n\nAlternatively (if you don\u2019t want to run `composer update`), you can manually look inside your error views in \u201c*resources/views/errors*\u201d and output `e($exception-\u003egetMessage())` instead of `$exception-\u003egetMessage()`. That\u2019s all there is to the fix, really.\n\n### What the maintainers have done about this\n\nActed as soon as our team found it (last week of March 2022):\n- Pushed patches to 5.x, 4.1 and 4.0;\n- Made it easy to apply the fix to existing projects, using a new `php artisan backpack:fix` command;\n- Kept the specific circumstances a secret; as far as we know, only our team knows about the niche case where this exploit is possible;\n- Emailed all our licensed users, to have a chance to fix their projects before it\u2019s public;\n- Sent an email blast to our 25.000+ strong Security Newsletter;\n- Made this public with a blog post and soon a CVE, after our community has had a reasonable chance to fix their projects;\n- Will continue to monitor this and remind paying users to apply this fix if they haven\u2019t;\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [backpack/crud](https://github.com/laravel-backpack/crud)\n* Email us at [hello@backpackforlaravel.com](mailto:hello@backpackforlaravel.com)\n\n---\n\nPS. You can [read this blog post](https://backpackforlaravel.com/articles/news/we-recommend-you-fix-this-vulnerability) for more information.",
"id": "GHSA-m8xx-3x29-84h8",
"modified": "2026-06-03T20:29:20Z",
"published": "2026-06-03T20:25:50Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Laravel-Backpack/CRUD/security/advisories/GHSA-m8xx-3x29-84h8"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31114"
},
{
"type": "WEB",
"url": "https://backpackforlaravel.com/articles/news/we-recommend-you-fix-this-vulnerability"
},
{
"type": "PACKAGE",
"url": "https://github.com/Laravel-Backpack/CRUD"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N",
"type": "CVSS_V4"
}
],
"summary": "backpack/crud is vulnerable to Cross-Site Scripting (XSS)"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.