Security readout for executives and security teams
Plain-English summary
Adobe Campaign Classic has a critical SQL injection flaw that may let an unauthenticated remote attacker run code with the application user’s privileges. No user action is required, although exploitation depends on conditions outside the attacker’s control. Compromise could affect data confidentiality, integrity, availability, and connected systems.
Executive priority
Treat as an immediate remediation priority where Adobe Campaign Classic is deployed. Establish ownership, determine external reachability, confirm versions, and follow Adobe’s advisory. Highest urgency applies to exposed systems because exploitation needs neither credentials nor user interaction, despite requiring favorable conditions.
Technical view
CVE-2026-48381 is a CWE-89 SQL injection vulnerability with CVSS 3.1 score 9.0. The vector indicates network access, high attack complexity, no privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. The source identifies ACC v7 7.4.4 build 9400 as affected, but does not clearly define the complete version range.
Likely exposure
Prioritize internet-accessible or otherwise untrusted-network-reachable Adobe Campaign Classic deployments. The supplied affected-version data explicitly names ACC v7 7.4.4 build 9400 and also contains an unexplained “0” entry, so the complete affected range is uncertain. Confirm all installed versions against Adobe’s advisory.
Exploitation context
The source states that exploitation is remote, unauthenticated, requires no user interaction, and could execute arbitrary code as the current user. Attack complexity is high because exploitation depends on conditions outside the attacker’s control. The CVE is not listed as KEV, and the bundle provides no evidence of active exploitation or public exploit availability.
Researcher notes
The stated impact escalates from SQL injection to arbitrary code execution in the current user context, with changed scope. The bundle does not identify the vulnerable component, request path, required environmental conditions, patch version, indicators of compromise, or complete affected-version boundaries. Avoid assuming that only build 9400 is affected until Adobe’s advisory is reviewed.
Mitigation direction
- Review Adobe advisory APSB26-123 and apply its prescribed update or mitigation.
- Inventory Adobe Campaign Classic instances and identify their exact versions and build numbers.
- Restrict untrusted network access to affected instances while remediation is pending.
- Protect backups and verify recovery procedures before applying vendor-directed changes.
Validation and detection
- Confirm each Adobe Campaign Classic version and build against APSB26-123.
- Verify vendor-directed updates or mitigations are present on every instance.
- Confirm affected services are not unnecessarily reachable from untrusted networks.
- Review application, database, and security logs for unexplained queries, errors, or code execution.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-48381 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26adobeVulnerability scoring details
Base CVSS 3.1 score
9CriticalVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://helpx.adobe.com/security/products/campaign/apsb26-123.htmlCVE reference, adobe · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.