Skip to main content

Adobe Campaign Classic EUVDEUVD-2026-84654

| CVE-2026-82008 CRITICAL
Improper Input Validation (CWE-20)
2026-09-22 adobe GHSA-hh8q-72c9-fr8x
9.9
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged ACC user
  2. Delivery
    Submit crafted unvalidated input to ACC endpoint
  3. Exploit
    Trigger improper input validation (CWE-20)
  4. Execution
    Execute arbitrary code as current user
  5. Impact
    Pivot across changed scope boundary

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Requires a low-privileged authenticated account on the target Adobe Campaign Classic instance (PR:L) that can reach the vulnerable input-processing component over the network (AV:N). No user interaction is required (UI:N) and attack complexity is low (AC:L), so once an attacker has any valid low-privilege ACC credential the flaw is directly reachable. The limiting factor is therefore the authentication requirement: this is not exploitable by a fully anonymous remote attacker. The specific vulnerable feature/endpoint and the input that triggers CWE-20 are not named in the sparse APSB26-142 advisory, so precise reachability should be confirmed against Adobe's guidance and the fixed build applied.

Impact

This is a genuinely high-priority vulnerability by CVSS math (9.9) but the exploitation signals are thin. The vendor-supplied vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H describes a network-reachable, low-complexity flaw requiring only low privileges and no user interaction, with a scope change and full CIA impact - arbitrary code execution in the current user's context. All three exploitation-likelihood signals are absent: no EPSS score is provided, the CVE is not in CISA KEV, and no POC has surfaced. Exploitation status is therefore 'no public exploit identified at time of analysis.' The internal consistency between the CWE-20 (improper input validation → ACE) description and the CVSS vector is good - the PR:L in the vector matches the 'low-privileged attacker' language in the description, so the authenticated qualifier is supportable. Key caveats: this is a single-source, Adobe-self-reported advisory (APSB26-142) with no independent corroboration, no fixed build number is published in the input, and no affected/fixed version boundaries are given in the CPE (wildcard). Net: treat as a real priority for organizations running ACC because it requires only low-privilege access and yields code execution across a scope boundary, but note that real-world exploitation is not yet demonstrated and the advisory detail is sparse.

Exploit ScenarioDerived

An attacker who already holds a low-privileged authenticated foothold in an Adobe Campaign Classic instance (e.g., a limited operator account) submits crafted input to a network-reachable ACC component that fails to validate it, triggering arbitrary code execution in the context of the current user without any interaction from another user. Because scope is changed, the resulting code execution can affect resources beyond the initially vulnerable component. No public exploit code is currently identified.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 1.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 22, 2026

Arbitrary code execution in Adobe Campaign Classic allows a low-privileged authenticated attacker to run code in the context of the current user without any victim interaction, because the platform fails to properly validate input reaching an exposed processing component. The flaw scores 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), and its scope change means a successful exploit can affect resources beyond the vulnerable component, raising the blast radius for confidentiality, integrity, and availability. The decisive prerequisite is authentication: per the assessed vector (PR:L), any valid low-privilege ACC account that can reach the component over the network is enough, but a fully anonymous remote attacker cannot trigger it; there is no public exploit identified at time of analysis and no CISA KEV confirmation of active exploitation, so the exploitation signals remain thin even though the severity math is high.

RemediationAI

Patch status for this issue should be taken directly from Adobe's advisory APSB26-142 (https://helpx.adobe.com/security/products/campaign/apsb26-142.html); the supplied data references that vendor advisory but does not enumerate an exact fixed build, so upgradefirst to the version Adobe lists as remediated for this CVE rather than relying on a version number quoted elsewhere, and treat any build not explicitly covered by the bulletin as unverified. Because exploitation requires only a low-privileged account (PR:L) and no user interaction, the most effective compensating controls until the fixed build is deployed are identity and exposure reduction: audit and disable dormant or unnecessary Campaign Classic operators and tighten the privilege/role assignments of remaining accounts, since every valid low-privilege login is a potential foothold; the trade-off is operational friction for legitimate marketing users who lose role scope. Restrict network access to the ACC web/API endpoints to trusted management networks or VPN rather than publishing them to the general internet, accepting reduced remote-access convenience for distributed teams. If specific vulnerable web applications, JSSP scripts, or workflow features can be identified from Adobe's guidance, disable or unpublish those that are not business-critical, understanding that disabling them may break dependent campaigns. Add compensating detection at the edge (WAF rules for anomalous parameter payloads, and alerting on unexpected child-process or interpreter spawning by the ACC service account), but treat these as detection layers only - they do not substitute for applying the vendor fix.

Affected VersionsENISA

Adobe Campaign Classic 0 ≤7.4.4 build 9401

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The reported root cause class is CWE-20 (Improper Input Validation), meaning a server-side component of Adobe Campaign Classic consumes externally supplied data without confirming its type, length, format, or permitted values, so crafted input can be passed into a processing path that then executes attacker-influenced content in the context of the running ACC user. The affected product is the on-premises/hosted enterprise marketing automation platform, identified by the CPE cpe:2.3:a:adobe:adobe_campaign_classic:*:*:*:*:*:*:*:* with a wildcard version, so no specific build range is enumerated in the supplied data. The assessed vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H indicates the attack is network reachable with low complexity and requires only a low-privileged account, no user interaction, and that a successful exploit crosses a security scope boundary - a classic sign that a low-privilege component can reach privileged execution or host-level resources. Notably, neither Adobe's advisory APSB26-142 nor the provided intelligence names the specific vulnerable feature, endpoint, or the exact malformed input that triggers CWE-20, so precise reachability from a given low-privilege role should be confirmed against Adobe's guidance rather than assumed from the score alone.

Know when Adobe Campaign Classic gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (adobe) PRIMARY 9.9 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.9 CRITICAL

Network-reachable, low-complexity code execution needing only a low-privilege ACC account (PR:L), no interaction, with a scope change and full CIA impact - matches vendor vector.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Adobe Campaign Classic (ACC) is affected by an Improper Input Validation vulnerability that could result in arbitrary code execution in the context of the current user. A low-privileged attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.

Executive ViewAI

Why It Matters

Adobe Campaign Classic, a critical marketing automation platform, contains a maximum-severity arbitrary code execution flaw that allows an authenticated low-privileged attacker to run code without user interaction, potentially compromising data integrity and confidentiality across interconnected systems. No vendor-released patch identified at time of analysis, and while no public exploit identified at time of analysis, the combination of high severity, scope change, and authentication requirement means malicious insiders or compromised low-privilege accounts pose a significant risk. Leadership should prioritize immediate mitigations to protect sensitive customer data and maintain regulatory compliance.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting network access to the exposed component, enforcing least privilege and multi-factor authentication, enabling detailed logging and monitoring, and deploying virtual patching via WAF if feasible.

Threat Intelligence Overview

EPSS Score
1.2%
Top 33% exploitable
Prevalence
Medium
Adobe enterprise marketing-automation platform, common in large orgs but not ubiquitous
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 1.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2026-75703 CRITICAL
10.0 Sep 22

Arbitrary code execution in Adobe Campaign Classic, documented in Adobe security advisory APSB26-142, lets remote attack

CVE-2026-84412 CRITICAL
10.0 Sep 22

Unauthenticated remote code execution in Adobe Campaign Classic lets any attacker who can reach the server run arbitrary

CVE-2026-75721 CRITICAL
10.0 Sep 22

Unauthenticated remote code execution in Adobe Campaign Classic (ACC) allows a network-reachable attacker to execute arb

CVE-2026-75699 CRITICAL
10.0 Sep 22

Unauthenticated remote code execution in Adobe Campaign Classic allows an attacker who can reach the application to exec

CVE-2026-73369 CRITICAL
10.0 Sep 22

Remote, unauthenticated attackers can execute arbitrary code in the context of the current application user on systems r

CVE-2026-89275 CRITICAL
10.0 Sep 22

Code injection in Adobe Campaign Classic allows remote attackers to execute arbitrary code in the context of the current

CVE-2026-75723 CRITICAL
10.0 Sep 22

Remote code execution in Adobe Campaign Classic allows an unauthenticated network attacker to invoke functionality that

CVE-2026-76195 CRITICAL
10.0 Aug 25

Arbitrary code execution in Adobe Campaign Classic (ACC) arises from OS command injection (CWE-78), letting an attacker

CVE-2026-76197 CRITICAL
10.0 Aug 25

OS command injection in Adobe Campaign Classic (ACC) allows an attacker to execute arbitrary operating-system commands,

CVE-2026-83660 CRITICAL
10.0 Sep 22

Server-side request forgery in Adobe Campaign Classic (versions up to and including 7.4.4 build 9401) lets remote unauth

CVE-2026-48330 CRITICAL
10.0 Aug 03

SQL injection in Adobe Campaign Classic (ACC) lets a remote, unauthenticated attacker inject arbitrary SQL commands that

CVE-2026-48323 CRITICAL
10.0 Aug 03

Remote code execution in Adobe Campaign Classic (ACC) arises from server-side template injection (CWE-1336), where impro

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy