A CVSS score compresses several decisions into one number. For Adobe Campaign Classic, the vectors in APSB26-162 show why the October 2026 update covers more than one kind of attacker. CVE-2026-104350 is a critical reflected XSS issue, but the same build fixes command execution and SQL injection paths with different access requirements.
The primary XSS vector
CVE-2026-104350 has a CVSS 3.1 base score of 9.3. Its vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N. Each field explains a constraint on the attack.
Network access means the issue can be reached over a network path, which can include a crafted URL delivered through ordinary messaging. Low complexity means the attacker does not need a special race condition or unusual target configuration beyond the vulnerable application. No privileges means the attacker does not need a Campaign account. User interaction is required, so a victim must perform the action that activates the reflected content.
Scope is changed, which means the impact can cross a security boundary around the vulnerable component. Confidentiality and integrity are high, while availability is none. Adobe lists privilege escalation as the impact. The practical target is the victim's browser session and the authority attached to it, not a direct denial of service.
What user interaction does not mean
A required click or URL visit can sound like a weak condition. The CVSS score already accounts for it, and the resulting score remains critical. Campaign users work with links, approvals, and reports every day. A well-timed message can fit that behavior without requiring a technical exploit from the victim.
The attacker still needs delivery and timing. The public advisory does not provide the affected parameter or a working payload. That limits reproduction claims and means defenders cannot assume that any URL containing script text is the exact exploit path. The condition should guide monitoring without becoming an excuse for delay.
Compare the other paths
Three Campaign Classic CVEs at 9.9 use low privileges and no user interaction. CVE-2026-104351 is code injection, CVE-2026-104353 is OS command injection, and CVE-2026-105780 is incorrect authorization. Each is linked to arbitrary code execution. A stolen or low-privilege Campaign account may be enough to reach these paths depending on the affected interface and role.
CVE-2026-105489 is a 9.9 SQL injection issue associated with security feature bypass and low privileges. CVE-2026-105781 is rated 9.8 by Adobe and has no privileges or user interaction in its vector, making it the most accessible non-XSS entry in the bulletin's matrix. CVE-2026-104354 is a 9.1 SQL injection issue with high privileges, and CVE-2026-105779 is a 9.1 SQL injection issue with low privileges.
Those differences matter for finding ownership. The web team may own the XSS surface, the database team may care about SQL injection, and application administrators control the roles behind command execution paths. One patch reunites those owners around the same build.
Map the reachable interface
For CVE-2026-104350, identify where Campaign users open browser sessions and what identity provider controls access. For the command execution entries, identify which accounts can call administrative functions or reach the relevant components. For SQL injection, understand which web and integration paths can query Campaign data.
The public bulletin does not map every CVE to a separate exposed port or endpoint. Use the interfaces the product actually presents in the deployment, then validate access with the system owner. Do not invent network diagrams from CVSS fields.
A Campaign environment may have a web interface, desktop client, application servers, database links, and delivery connectors. Each adds a different reachable surface. The task is to determine which surfaces carry which user authority and whether an attacker can reach them from a lower-trust network.
Use exposure data as a lead
A ZoomEye query for title="Adobe Campaign" returned 149 page-title matches during this review. This is a broad product-page observation, not a set of confirmed vulnerable hosts. The exact CVE filter returned zero, showing that public indexing does not provide a complete inventory of affected Campaign deployments.
Use the page matches to find interfaces that may be internet visible. Then check whether the page is still active, who owns it, and which Campaign build it runs. A public page that returns after a patch may be benign, while an untracked internal system at build 9402 can remain the more important exposure.
Translate the matrix into action
Adobe reports no known in-the-wild exploitation for the bulletin at publication time. That gives teams a chance to patch before evidence of targeting changes the urgency. It does not reduce the severity of the defects.
The direct action is build 9403. Prioritize systems where the reflected XSS can reach high-authority users or where the low-privilege code execution and SQL injection vectors are exposed to broad account populations. Track each system by build state, owner, data sensitivity, and access path. The CVSS vectors explain why a single patch priority can still produce different operational risks across the estate.