The CVSS 7.2 rating for this vulnerability is misleading and should not drive your prioritization decisions. The actual exploit chain begins with the backup restore function—an often-forgotten code path that loads schema files and executes their contents unconditionally. The SQL injection that the CVSS vector references is not the initial compromise vector; it's a post-exploitation mechanism for data extraction once PHP execution is achieved through the schema-loading mechanism.
The critical vulnerability is this: baserCMS's schema file loading treats PHP code in schema files as inert configuration rather than executable code. This means any injection into a schema file—whether through backup restore or other file-writing pathways—results in immediate, unconditional PHP execution. The PostgreSQL specificity is significant because error-based SQL injection extraction depends on verbose error messaging, suggesting the attacker or researcher has specific PostgreSQL expertise.
Your immediate actions: First, audit who can access the backup restore function in your baserCMS deployment. If it accepts input from users below administrator privilege, you have a critical unauthenticated or low-privilege exposure. Second, verify whether the schema loader's unconditional execution model exists elsewhere in your installation—this pattern, not just this specific injection point, is the vulnerability class. Third, if you're on shared hosting with a shared PostgreSQL instance, treat any compromise of the backup restore function as lateral movement risk to adjacent tenant databases; the CVSS privilege rating doesn't capture this post-exploitation pivot potential.
The deeper concern is architectural. This schema-loading-as-execution pattern has appeared in WordPress plugins and Drupal hook implementations—the same genetic defect wearing different syntax. Patching this specific CVE without addressing the underlying assumption that schema files are inert configuration will produce future variants. Your long-term response should be auditing all schema-loading paths in baserCMS and its plugins, not just the backup restore endpoint.