LiveActive security incident?Get immediate response
CVE Record

CVE-2026-48381: Adobe Campaign Classic (ACC) | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (CWE-89)

Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction. Scope is changed.

CriticalCVSS 9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

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 execute code with the application's user privileges. No user action is required, although exploitation depends on conditions outside the attacker's control. Compromise could expose data, alter systems, or disrupt service.

Executive priority

Treat as an urgent remediation item because successful exploitation could cross security boundaries and severely affect data and service availability. Immediately identify exposed Campaign Classic deployments, confirm applicability with Adobe, and schedule vendor-prescribed remediation. Escalate internet-reachable affected systems, while recognizing that the available sources do not establish active exploitation.

Technical view

CVE-2026-48381 is a CWE-89 SQL injection vulnerability rated CVSS 9.0. The supplied vector indicates remote access, high attack complexity, no required privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. Successful exploitation can produce arbitrary code execution in the current user's context.

Likely exposure

Prioritize Adobe Campaign Classic deployments matching the source bundle's listed ACC v7 7.4.4 build 9400 entry, especially network-reachable instances. The bundle also contains an ambiguous version value of “0” and marks unspecified versions unaffected; confirm exact applicability through Adobe's advisory rather than extrapolating additional affected releases.

Exploitation context

The CVSS vector supports remote, unauthenticated exploitation without user interaction, but attack complexity is high and exploitation requires conditions beyond the attacker's control. The bundle reports no CISA KEV listing and provides no evidence of active exploitation or a public exploit.

Researcher notes

The source bundle identifies SQL injection leading to code execution, but does not describe the vulnerable component, required environmental conditions, attack surface, indicators of compromise, or fixed release. The affected-version data is unusually formatted, so precise scoping requires APSB26-123. Avoid treating CVSS network reachability as proof that every deployment is internet exploitable.

Mitigation direction

  • Review Adobe advisory APSB26-123 for the vendor-approved remediation and affected-version details.
  • Inventory Campaign Classic versions and builds, prioritizing the explicitly listed ACC v7 build.
  • Restrict unnecessary network access to Campaign Classic while remediation is evaluated or applied.
  • Apply Adobe's prescribed update or mitigation after validating operational compatibility.
  • Monitor affected systems for suspicious database, application, and process activity.

Validation and detection

  • Record each Campaign Classic instance's exact version and build number.
  • Compare inventory directly with APSB26-123; do not infer affected version ranges.
  • Confirm whether relevant Campaign Classic interfaces are reachable from untrusted networks.
  • Review application, database, and host logs for anomalous queries, errors, or processes.
  • After remediation, verify the installed build and repeat exposure checks.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

Execution 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 lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-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
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26adobe

Vulnerability scoring details

Base CVSS 3.1 score

9Critical
CVSS 3.1 vector shape for CVE-2026-48381Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdobeAdobe Campaign Classic0, ACC v7: 7.4.4 build 9400unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

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.