dbcve.org
CampaignApplication · Adobe

CVE-2026-48303

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 7.4.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Campaign Classic (ACC) versions 7.4.3 build 9394 and earlier are affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction. Scope is changed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe Campaign Classic versions 7.4.3 build 9394 and earlier contain an Incorrect Authorization vulnerability that allows unauthenticated attackers to achieve arbitrary code execution in the context of the current user without any user interaction. The scope has changed, indicating the vulnerability can impact components beyond the original security boundary.

MitigationApply the vendor-provided patch or upgrade Adobe Campaign Classic to a version beyond 7.4.3 build 9394 immediately, as this is a critical severity vulnerability with known public exploitation potential.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CampaignApplication
Affected:< 7.4.3= 7.4.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Adobe Campaign Classic version
    Access the Adobe Campaign client console, navigate to Help > About, or check the version.xml/config.xml file in the installation directory to identify the installed version number.
    Affected if Version is 7.4.3 or earlier (any 7.x version below 7.4.3, or exactly 7.4.3)
  2. Check Adobe Campaign build number
    In the Adobe Campaign client console, go to Help > About or check the build information in the server configuration files (e.g., serverConf.xml) to identify the build number.
    Affected if Build number is 9394 or earlier (including build 9394)
  3. Confirm version via Campaign server
    Access the Campaign server's administration interface or check the version information returned by the server startup logs or installation metadata files on the server filesystem.
    Affected if The server reports version 7.4.3 with build 9394 or lower, or any version prior to 7.4.3
  4. Identify if web interface is exposed
    Verify if the Adobe Campaign web (Tomcat) interface is accessible externally by attempting to reach standard endpoints like /nl/jsp/ or /campaign/ on the server.
    Affected if The web interface is exposed and the version/build check above confirms a vulnerable release

You are affected if your installed Adobe Campaign Classic version is 7.4.3 with build 9394 or earlier, or any version of 7.x prior to 7.4.3.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.4.3 or later
Fixed in 7.4.3
Interim mitigation

Apply the vendor-provided patch or upgrade Adobe Campaign Classic to a version beyond 7.4.3 build 9394 immediately, as this is a critical severity vulnerability with known public exploitation potential.

Recommended fix Moderate confidence

Adobe Campaign Classic 7.4.4 or later (or latest available 7.x release)

  1. 1. Identify the current Adobe Campaign Classic (ACC) version by checking the build number in the Adobe Campaign client console or server logs
  2. 2. Backup the current ACC instance including database, configuration files, and custom code
  3. 3. Download the latest Adobe Campaign Classic version from Adobe's official distribution channels (Adobe Exchange or through your Adobe contract)
  4. 4. Review Adobe's upgrade documentation for ACC 7.x to understand the migration process
  5. 5. Test the upgrade in a non-production environment first to ensure compatibility with existing workflows and integrations
  6. 6. Execute the upgrade following Adobe's recommended upgrade procedure
  7. 7. Verify the build number reflects a version newer than 7.4.3 (build 9394)
  8. 8. Test critical workflows and confirm the application functions correctly post-upgrade
Caveat Review Adobe's release notes for 7.4.4+ for any configuration or workflow changes that may require adjustments; custom JavaScript code or integrations may need testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Campaign Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48303 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48303 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data