CVE-2026-47938
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 · uneditedAdobe Campaign Classic (ACC) versions 7.4.3 build 9394 and earlier are affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation. 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 confidenceAdobe Campaign Classic versions 7.4.3 build 9394 and earlier contain a Server-Side Request Forgery (SSRF) vulnerability that allows attackers to coerce the server into making arbitrary HTTP requests to internal or external resources. The changed scope indicates the vulnerability impacts components beyond the immediate application, and the CVSS 10 score reflects the severity of potential privilege escalation achievable without any user interaction.
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<= 7.4.2= 7.4.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Adobe Campaign Classic is installedLocate Adobe Campaign Classic installation directory or check for associated services/processes on the server. Look for 'nlserver' process or campaign-related directories.Affected if Adobe Campaign Classic is found on the system
-
Determine the installed version and build numberAccess the Adobe Campaign Classic client console or check version files in the installation directory. The build number is typically displayed in the About section or in configuration XML files.Affected if The build number is 9394 or earlier, or the version is 7.4.3 with build 9394 or earlier
-
Verify the web or API interface is accessibleCheck if the Adobe Campaign Classic web module (Tomcat/Apache) is running and accessible. Test connectivity to standard campaign ports (8080, 80, 443, or configured ports).Affected if The web interface is exposed and reachable from network segments where exploitation could occur
-
Check for outbound network configurationInspect network configuration files or firewall rules allowing the application server to make outbound HTTP/HTTPS connections.Affected if The application server has unrestricted outbound network access, allowing SSRF to reach internal services
-
Review user access to campaign workflows and triggersIdentify which user roles have access to features that can trigger HTTP requests, such as web apps, workflows with external calls, or data import from URLs.Affected if Low-privileged users can trigger external requests through campaign features
You are affected if Adobe Campaign Classic version 7.4.3 build 9394 or earlier is installed and the web interface or campaign workflow features are accessible, as this enables SSRF exploitation.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe Campaign Classic to version 7.4.3 build 9395 or later to obtain the patched version that addresses this SSRF vulnerability.
Latest Adobe Campaign Classic version after 7.4.3 build 9394 (consult helpx.adobe.com for the exact fixed build number)
- 1. Check the current Adobe Campaign Classic version by reviewing the build number in the installation or console
- 2. Navigate to the Adobe Campaign Classic security updates page at helpx.adobe.com for the latest security bulletin
- 3. Download the latest Adobe Campaign Classic update or hotfix that addresses CVE-2026-47938
- 4. Before applying the update, back up the Adobe Campaign database and configuration files
- 5. Apply the upgrade following Adobe's standard upgrade procedures for ACC
- 6. Verify the new build version matches the fixed release version from the security bulletin
- 7. Test critical workflows to ensure the upgrade did not break existing functionality
- 8. Review system logs to confirm the SSRF vulnerability has been mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47938 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47938 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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