Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker could exploit this vulnerability to gain elevated privileges. Exploitation of this issue does not require user interaction.
Security readout for executives and security teams
Plain-English summary
Adobe Campaign Classic has a critical authorization flaw that may let a remote, unauthenticated attacker gain elevated privileges without user action. Successful exploitation could expose or alter sensitive campaign data and disrupt service. The supplied version information is ambiguous, so organizations should confirm affected builds directly against Adobe’s advisory.
Executive priority
Treat as an urgent remediation item because compromise could affect customer data, campaign integrity, and platform availability without user action. Require rapid inventory and vendor-guided remediation, while avoiding claims of active exploitation unsupported by current evidence.
Technical view
CVE-2026-48333 is an incorrect authorization vulnerability (CWE-863) in Adobe Campaign Classic. Its CVSS 3.1 score is 9.8: network-accessible, low complexity, no privileges or user interaction required, with potentially high confidentiality, integrity, and availability impact. The bundle identifies ACC v7 build information but does not clearly distinguish vulnerable from corrected builds.
Likely exposure
Exposure is most concerning where Adobe Campaign Classic services are network-accessible. The supplied data mentions ACC v7 7.4.3 build 9399, but its exact affected-or-fixed status is unclear. Inventory all ACC deployments and compare their versions and configurations with Adobe APSB26-120.
Exploitation context
The scoring indicates potential remote, unauthenticated exploitation without user interaction. However, the bundle does not include technical attack details, proof-of-concept evidence, or reports of exploitation in the wild. The CVE is not listed as KEV in the supplied data.
Researcher notes
The authorization weakness is categorized as CWE-863, but the bundle provides no vulnerable component, request path, root cause, or exploit evidence. The version entry is insufficiently precise for definitive exposure decisions. Researchers and vulnerability managers should use Adobe APSB26-120 as the authoritative source for build applicability and remediation.
Mitigation direction
Review Adobe APSB26-120 and apply the vendor-prescribed update or mitigation.
Inventory all Adobe Campaign Classic instances, including externally hosted and managed deployments.
Prioritize systems reachable from untrusted networks or handling sensitive customer data.
If remediation is delayed, follow Adobe guidance for temporary exposure reduction and monitoring.
Validation and detection
Record each ACC version and build, then compare them with Adobe APSB26-120.
Confirm the vendor-prescribed remediation is installed on every identified instance.
Verify internet-facing and administrative access paths are intentionally required and documented.
Review authentication, privilege, and administrative logs for unexplained elevated access.
Reassess affected status after Adobe clarifies or updates its advisory.
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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.