Publish GHSA-cpv7-q2wx-m8rw

Author: advisory-database[bot]

advisories/github-reviewed/2026/03/GHSA-cpv7-q2wx-m8rw/GHSA-cpv7-q2wx-m8rw.json

@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-cpv7-q2wx-m8rw",
-  "modified": "2026-03-01T01:30:55Z",
+  "modified": "2026-03-25T20:57:24Z",
   "published": "2026-03-01T01:30:55Z",
   "aliases": [
     "CVE-2026-28425"
   ],
   "summary": "Statamic vulnerable to remote code execution via Antlers-enabled control panel inputs",
-  "details": "### 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.11 and 6.4.0. If developers use addons that depend on Statamic, ensure that a patched version of Statamic is running.",
+  "details": "### 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.",
   "severity": [
     {
       "type": "CVSS_V3",
@@ -28,7 +28,7 @@
               "introduced": "0"
             },
             {
-              "fixed": "5.73.11"
+              "fixed": "5.73.16"
             }
           ]
         }
@@ -47,7 +47,7 @@
               "introduced": "6.0.0-alpha.1"
             },
             {
-              "fixed": "6.4.0"
+              "fixed": "6.7.2"
             }
           ]
         }
@@ -69,11 +69,11 @@
     },
     {
       "type": "WEB",
-      "url": "https://github.com/statamic/cms/releases/tag/v5.73.11"
+      "url": "https://github.com/statamic/cms/releases/tag/v5.73.16"
     },
     {
       "type": "WEB",
-      "url": "https://github.com/statamic/cms/releases/tag/v6.4.0"
+      "url": "https://github.com/statamic/cms/releases/tag/v6.7.2"
     }
   ],
   "database_specific": {