Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged ACC user
-
DeliverySubmit malformed input to vulnerable component
-
ExploitBypass improper input validation
-
ExecutionAchieve arbitrary code execution as current user
-
ImpactPivot across changed scope to impact confidentiality/integrity/availability
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 an authenticated low-privileged account on the Adobe Campaign Classic instance (PR:L) and network reachability to the application (AV:N); no user interaction is needed (UI:N). Exploitation is additionally gated by conditions outside the attacker's control per Adobe (reflected as AC:H) - i.e. specific environmental, timing, or deployment state must hold, so this is not a reliably reproducible remote attack against arbitrary default installs. The vulnerable path is an ACC component that improperly validates attacker-supplied input; the exact feature/endpoint is not named in the advisory summary. Limiting factors: valid credentials required, high attack complexity, and impact confined to code execution in the current user's context (though scope-changed to affect adjacent resources). |
| Impact | CVSS 3.1 base score is 8.5 (HIGH) via CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - network-reachable, but the AC:H flag is significant: Adobe's own text 'Exploit depends on conditions beyond the attacker's control' means reliable exploitation is gated on environmental/timing factors, not merely attacker skill. PR:L confirms an authenticated (low-privileged) attacker is required per the vector. No EPSS score, no CISA KEV listing, and no public POC are present in the supplied intelligence, so exploitation status is 'no public exploit identified at time of analysis.' There is no SSVC decision record in the input. Signals are internally consistent (self-reported by Adobe, single vendor advisory) rather than conflicting, but they point to a real-but-non-trivial issue: full C/I/A impact and scope change raise theoretical severity, while AC:H plus required authentication materially lower the probability of widespread opportunistic exploitation. This reads as a genuine patch-priority item for ACC operators but not an emergency drop-everything CVE absent evidence of active exploitation. Note the vector's C:H/I:H/A:H is Adobe-supplied and not independently verified by NVD in the provided data. |
| Exploit ScenarioDerived | A low-privileged authenticated user of an Adobe Campaign Classic instance submits crafted input to a component that improperly validates it, triggering arbitrary code execution in the context of the current user. Because scope is changed, the resulting execution can affect resources beyond the initially vulnerable component. No public exploit code is identified, and reliable exploitation depends on environmental conditions outside the attacker's direct control (AC:H). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Improper input validation in Adobe Campaign Classic allows a low-privileged, authenticated attacker with network reachability to achieve arbitrary code execution in the context of the current user, with the impact scoped beyond the vulnerable component (CVSS 3.1 base 8.5, AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H). No user interaction is required, but Adobe explicitly notes that exploitability depends on conditions beyond the attacker's control, reflected as AC:H - meaning successful exploitation is gated by specific environmental, timing, or deployment state rather than being a reliably reproducible remote attack against default installs. There is no public exploit identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing), and the specific vulnerable feature or endpoint is not named in the advisory summary.
RemediationAI
Apply the fix identified in Adobe Security Bulletin APSB26-142 (https://helpx.adobe.com/security/products/campaign/apsb26-142.html); the provided data does not confirm an exact patched version string, so verify the recommended build directly against the bulletin before considering an instance remediated. Until the fixed build is confirmed in place, reduce exposure with targeted compensating controls: restrict network access to the Adobe Campaign Classic application so that only trusted operator networks and integration sources can reach it (trade-off: may break remote or third-party campaign integrations and require VPN/allow-list maintenance), and review and trim accounts holding low-privileged roles so that only staff who genuinely need them retain access (trade-off: operational overhead and possible workflow disruption for marketing users). Where feasible, add input-validation-focused monitoring or filtering at the application's front door - for example, logging and alerting on anomalous parameter payloads to Campaign endpoints - while recognizing that signature-based filtering is unlikely to catch every variant of an input-validation flaw and can produce false positives. Because exploitation is authenticated and depends on conditions outside the attacker's control, prioritize credential hygiene, session monitoring for unexpected account behavior, and prompt upgrade when the vendor-patched build is available, rather than relying on network controls alone.
Affected VersionsENISA
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 root cause is CWE-20 (Improper Input Validation): an Adobe Campaign Classic component fails to properly validate attacker-supplied input before using it in a security-relevant operation, enabling arbitrary code execution. Adobe Campaign Classic is an enterprise marketing-automation platform that handles campaign orchestration, customer data, and delivery workflows, typically exposed to internal operators and integration endpoints over the network, which is why the vector is AV:N with PR:L (a valid low-privileged account is required). The scope-changed rating (S:C) indicates that a successful exploit can affect resources beyond the vulnerable component's own security authority, so the practical blast radius may exceed the compromised user's nominal privileges, even though the CVSS vector states code execution occurs in the context of the current user. The AC:H component is material to risk assessment: per the vendor, exploitation depends on conditions outside the attacker's control, so this is a high-severity but not trivially repeatable attack path - the affected product is captured only as the wildcard CPE cpe:2.3:a:adobe:adobe_campaign_classic:*:*:*:*:*:*:*:*, meaning all versions are treated as potentially in scope pending the vendor's per-version guidance.
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
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Network-reachable but authenticated (PR:L) and gated by conditions beyond attacker control (AC:H); arbitrary code execution with scope change yields S:C and full C:H/I:H/A:H.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
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. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction. Scope is changed.
Executive ViewAI
Adobe Campaign Classic carries a high-severity input validation flaw (CVE-2026-82003) that would allow a low-privileged, authenticated user with network access to execute arbitrary code on the platform, with impact extending beyond the vulnerable component itself. Because this affects the system of record for marketing campaigns and the customer data it holds, successful exploitation could mean data exposure, unauthorized account actions, and operational disruption to revenue-generating campaign activity. No vendor patch is available, so the risk remains open and must be managed through compensating controls and exposure reduction in the near term.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network reachability to Adobe Campaign Classic management and application interfaces via VPN, IP allowlisting, or segmentation; enforce least privilege and remove or disable unnecessary low-privileged accounts; require MFA for all Campaign users; enable and monitor detailed authentication and application audit logs for anomalous activity; and apply virtual patching or filtering at the WAF/edge for unexpected input patterns to the Campaign application.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Adobe Campaign Classic
View allArbitrary code execution in Adobe Campaign Classic, documented in Adobe security advisory APSB26-142, lets remote attack
Unauthenticated remote code execution in Adobe Campaign Classic lets any attacker who can reach the server run arbitrary
Unauthenticated remote code execution in Adobe Campaign Classic (ACC) allows a network-reachable attacker to execute arb
Unauthenticated remote code execution in Adobe Campaign Classic allows an attacker who can reach the application to exec
Remote, unauthenticated attackers can execute arbitrary code in the context of the current application user on systems r
Code injection in Adobe Campaign Classic allows remote attackers to execute arbitrary code in the context of the current
Remote code execution in Adobe Campaign Classic allows an unauthenticated network attacker to invoke functionality that
Arbitrary code execution in Adobe Campaign Classic (ACC) arises from OS command injection (CWE-78), letting an attacker
OS command injection in Adobe Campaign Classic (ACC) allows an attacker to execute arbitrary operating-system commands,
Server-side request forgery in Adobe Campaign Classic (versions up to and including 7.4.4 build 9401) lets remote unauth
Arbitrary code execution in Adobe Campaign Classic allows a low-privileged authenticated attacker to run code in the con
SQL injection in Adobe Campaign Classic (ACC) lets a remote, unauthenticated attacker inject arbitrary SQL commands that
EUVD-2026-84662
GHSA-3fgx-p55x-rvwv
NVD
CVE.org
EPSS
Exploit-DB