{"items":[{"id":"NVI-00007071","kind":"vulnerability","title":"Statamic vulnerable to remote code execution via Antlers-enabled control panel inputs","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-cpv7-q2wx-m8rw","CVE-2026-28425"],"plain_summary":"OSV carries this publisher advisory for statamic/cms, statamic/cms. 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.73.16 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cd70cf8d82be1617ba2e501a0e615f2d"],"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 6.7.2 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cd70cf8d82be1617ba2e501a0e615f2d"],"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-153d0104b46dc943b50665258bcce0f7"],"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-06-17T10:28:35.963Z","value":"8 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-153d0104b46dc943b50665258bcce0f7"}],"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-cd70cf8d82be1617ba2e501a0e615f2d","url":"https://github.com/advisories/GHSA-cpv7-q2wx-m8rw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-cpv7-q2wx-m8rw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.702Z"},{"id":"sr-153d0104b46dc943b50665258bcce0f7","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-28425","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-28425","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:56.268Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cd70cf8d82be1617ba2e501a0e615f2d"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"### Impact\nAn authenticated control panel user with access to Antlers-enabled inputs may be able to achieve remote code execution in the application context. That can lead to full compromise of the application, including access to sensitive configuration, modification or exfiltration of data, and potential impact on availability.\n\nExploitation is only possible where Antlers runs on user-controlled content—for example, content fields with Antlers explicitly enabled (requiring permission to configure fields and to edit entries), built-in config that supports Antlers such as Forms email notification settings (requiring configuration permission), or third-party addons that add Antlers-enabled fields to entries (for example, the SEO Pro addon). In each case the attacker must have the relevant control panel permissions.\n\n### Patches\nThis has been fixed in 5.73.16 and 6.7.2.\n\nNote that a follow-up report showed that the original 5.73.11 & 6.4.0 fixes were insufficient.\n\nIf you use addons that depend on Statamic, ensure that after updating you are running a patched Statamic version.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.73.16"]},{"certainty":"source_listed","source_ids":["sr-cd70cf8d82be1617ba2e501a0e615f2d"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"### Impact\nAn authenticated control panel user with access to Antlers-enabled inputs may be able to achieve remote code execution in the application context. That can lead to full compromise of the application, including access to sensitive configuration, modification or exfiltration of data, and potential impact on availability.\n\nExploitation is only possible where Antlers runs on user-controlled content—for example, content fields with Antlers explicitly enabled (requiring permission to configure fields and to edit entries), built-in config that supports Antlers such as Forms email notification settings (requiring configuration permission), or third-party addons that add Antlers-enabled fields to entries (for example, the SEO Pro addon). In each case the attacker must have the relevant control panel permissions.\n\n### Patches\nThis has been fixed in 5.73.16 and 6.7.2.\n\nNote that a follow-up report showed that the original 5.73.11 & 6.4.0 fixes were insufficient.\n\nIf you use addons that depend on Statamic, ensure that after updating you are running a patched Statamic version.","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0-alpha.1; fixed 6.7.2"]}],"null_published_at":"2026-11-01T14:34:07.532Z","source_updated_at":"2026-03-25T21:22:48.425Z","source_disclosed_at":"2026-03-01T01:30:55.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:10.702Z"},{"id":"NVI-00007071","kind":"vulnerability","title":"Statamic vulnerable to remote code execution via Antlers-enabled control panel inputs","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-cpv7-q2wx-m8rw","CVE-2026-28425"],"plain_summary":"OSV carries this publisher advisory for statamic/cms, statamic/cms. 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.73.16 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cd70cf8d82be1617ba2e501a0e615f2d"],"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 6.7.2 for statamic/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-cd70cf8d82be1617ba2e501a0e615f2d"],"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-cd70cf8d82be1617ba2e501a0e615f2d","url":"https://github.com/advisories/GHSA-cpv7-q2wx-m8rw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-cpv7-q2wx-m8rw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.702Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-cd70cf8d82be1617ba2e501a0e615f2d"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"### Impact\nAn authenticated control panel user with access to Antlers-enabled inputs may be able to achieve remote code execution in the application context. That can lead to full compromise of the application, including access to sensitive configuration, modification or exfiltration of data, and potential impact on availability.\n\nExploitation is only possible where Antlers runs on user-controlled content—for example, content fields with Antlers explicitly enabled (requiring permission to configure fields and to edit entries), built-in config that supports Antlers such as Forms email notification settings (requiring configuration permission), or third-party addons that add Antlers-enabled fields to entries (for example, the SEO Pro addon). In each case the attacker must have the relevant control panel permissions.\n\n### Patches\nThis has been fixed in 5.73.16 and 6.7.2.\n\nNote that a follow-up report showed that the original 5.73.11 & 6.4.0 fixes were insufficient.\n\nIf you use addons that depend on Statamic, ensure that after updating you are running a patched Statamic version.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.73.16"]},{"certainty":"source_listed","source_ids":["sr-cd70cf8d82be1617ba2e501a0e615f2d"],"technology":"statamic/cms","known_exclusions":[],"conditions_summary":"### Impact\nAn authenticated control panel user with access to Antlers-enabled inputs may be able to achieve remote code execution in the application context. That can lead to full compromise of the application, including access to sensitive configuration, modification or exfiltration of data, and potential impact on availability.\n\nExploitation is only possible where Antlers runs on user-controlled content—for example, content fields with Antlers explicitly enabled (requiring permission to configure fields and to edit entries), built-in config that supports Antlers such as Forms email notification settings (requiring configuration permission), or third-party addons that add Antlers-enabled fields to entries (for example, the SEO Pro addon). In each case the attacker must have the relevant control panel permissions.\n\n### Patches\nThis has been fixed in 5.73.16 and 6.7.2.\n\nNote that a follow-up report showed that the original 5.73.11 & 6.4.0 fixes were insufficient.\n\nIf you use addons that depend on Statamic, ensure that after updating you are running a patched Statamic version.","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0-alpha.1; fixed 6.7.2"]}],"null_published_at":"2026-10-31T22:13:14.310Z","source_updated_at":"2026-03-25T21:22:48.425Z","source_disclosed_at":"2026-03-01T01:30:55.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:10.702Z"}],"next_cursor":null,"snapshot_revision":"42594"}