{"items":[{"id":"NVI-00003418","kind":"vulnerability","title":"backpack/crud is vulnerable to Cross-Site Scripting (XSS)","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m8xx-3x29-84h8","CVE-2022-31114"],"plain_summary":"GitHub lists this reviewed advisory for backpack/crud, backpack/crud, backpack/crud. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1e451aa7db16623e6e4d59ff2dc8deaa"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 5.0.13 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.69 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.0.63 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-21T19:10:00.107Z","value":"5.1 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-438859cb1a33b8205fac509a17d5572b"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.303%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.23087. Missing scores are unknown.","source_id":"sr-1e451aa7db16623e6e4d59ff2dc8deaa"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-3d472a4393786aa2dbaaa1b0f6514fa7","url":"https://github.com/advisories/GHSA-m8xx-3x29-84h8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m8xx-3x29-84h8","publisher":"GitHub Advisory Database","observed_at":"2026-11-07T00:53:06.181Z"},{"id":"sr-3dac180d94ec8c580e8aec89260fb547","url":"https://github.com/advisories/GHSA-m8xx-3x29-84h8","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m8xx-3x29-84h8","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.976Z"},{"id":"sr-438859cb1a33b8205fac509a17d5572b","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31114","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-31114","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:26.524Z"},{"id":"sr-1e451aa7db16623e6e4d59ff2dc8deaa","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2022-31114","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:42:56.080Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3d472a4393786aa2dbaaa1b0f6514fa7"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":[">= 5.0.0, < 5.0.13"]},{"certainty":"source_listed","source_ids":["sr-3d472a4393786aa2dbaaa1b0f6514fa7"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":[">= 4.1.0, < 4.1.69"]},{"certainty":"source_listed","source_ids":["sr-3d472a4393786aa2dbaaa1b0f6514fa7"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["< 4.0.63"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.13"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 4.1.0; fixed 4.1.69"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.0.63"]}],"null_published_at":"2026-11-07T14:01:55.411Z","source_updated_at":"2026-06-04T12:02:23.000Z","source_disclosed_at":"2026-06-03T20:25:50.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.976Z"},{"id":"NVI-00003418","kind":"vulnerability","title":"backpack/crud is vulnerable to Cross-Site Scripting (XSS)","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m8xx-3x29-84h8","CVE-2022-31114"],"plain_summary":"GitHub lists this reviewed advisory for backpack/crud, backpack/crud, backpack/crud. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-438859cb1a33b8205fac509a17d5572b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 5.0.13 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.69 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.0.63 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-21T19:10:00.107Z","value":"5.1 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-438859cb1a33b8205fac509a17d5572b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-3d472a4393786aa2dbaaa1b0f6514fa7","url":"https://github.com/advisories/GHSA-m8xx-3x29-84h8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m8xx-3x29-84h8","publisher":"GitHub Advisory Database","observed_at":"2026-11-07T00:53:06.181Z"},{"id":"sr-3dac180d94ec8c580e8aec89260fb547","url":"https://github.com/advisories/GHSA-m8xx-3x29-84h8","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m8xx-3x29-84h8","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.976Z"},{"id":"sr-438859cb1a33b8205fac509a17d5572b","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31114","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-31114","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:26.524Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3d472a4393786aa2dbaaa1b0f6514fa7"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":[">= 5.0.0, < 5.0.13"]},{"certainty":"source_listed","source_ids":["sr-3d472a4393786aa2dbaaa1b0f6514fa7"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":[">= 4.1.0, < 4.1.69"]},{"certainty":"source_listed","source_ids":["sr-3d472a4393786aa2dbaaa1b0f6514fa7"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["< 4.0.63"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.13"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 4.1.0; fixed 4.1.69"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.0.63"]}],"null_published_at":"2026-11-07T07:07:39.856Z","source_updated_at":"2026-06-04T12:02:23.000Z","source_disclosed_at":"2026-06-03T20:25:50.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.976Z"},{"id":"NVI-00003418","kind":"vulnerability","title":"backpack/crud is vulnerable to Cross-Site Scripting (XSS)","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m8xx-3x29-84h8","CVE-2022-31114"],"plain_summary":"OSV carries this publisher advisory for backpack/crud, backpack/crud, backpack/crud. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.0.13 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.69 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.0.63 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-438859cb1a33b8205fac509a17d5572b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-21T19:10:00.107Z","value":"5.1 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-438859cb1a33b8205fac509a17d5572b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-3dac180d94ec8c580e8aec89260fb547","url":"https://github.com/advisories/GHSA-m8xx-3x29-84h8","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m8xx-3x29-84h8","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.976Z"},{"id":"sr-438859cb1a33b8205fac509a17d5572b","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31114","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-31114","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:26.524Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.13"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 4.1.0; fixed 4.1.69"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.0.63"]}],"null_published_at":"2026-11-01T01:04:04.827Z","source_updated_at":"2026-09-10T03:51:09.191Z","source_disclosed_at":"2026-06-03T20:25:50.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.976Z"},{"id":"NVI-00003418","kind":"vulnerability","title":"backpack/crud is vulnerable to Cross-Site Scripting (XSS)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m8xx-3x29-84h8","CVE-2022-31114"],"plain_summary":"OSV carries this publisher advisory for backpack/crud, backpack/crud, backpack/crud. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.0.13 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.69 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.0.63 for backpack/crud. Confirm the publisher’s latest guidance.","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-3dac180d94ec8c580e8aec89260fb547","url":"https://github.com/advisories/GHSA-m8xx-3x29-84h8","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m8xx-3x29-84h8","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.976Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.13"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 4.1.0; fixed 4.1.69"]},{"certainty":"source_listed","source_ids":["sr-3dac180d94ec8c580e8aec89260fb547"],"technology":"backpack/crud","known_exclusions":[],"conditions_summary":"### Impact\n\nIt’s a “*moderate*” vulnerability… but being an admin panel, 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 - It should be made *impossible*. That’s why you are bothered with this. \n\n### Patches\n\n\nIf 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**:\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> **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’t want to run `composer update`), yo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.0.63"]}],"null_published_at":"2026-10-31T22:12:48.016Z","source_updated_at":"2026-09-10T03:51:09.191Z","source_disclosed_at":"2026-06-03T20:25:50.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.976Z"}],"next_cursor":null,"snapshot_revision":"42594"}