CVE-2024-47423
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 Framemaker versions 2020.6, 2022.4 and earlier are affected by an Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitrary code execution. An attacker could exploit this vulnerability by uploading a malicious file which can be automatically processed or executed by the system. Exploitation of this issue requires user interaction.
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 · moderate confidenceAdobe Framemaker versions 2020.6, 2022.4 and earlier contain an unrestricted file upload vulnerability where the application fails to properly validate uploaded file types before processing. An attacker can upload malicious files (e.g., executable scripts, DLLs, or other dangerous file types) that the system automatically processes or executes, leading to arbitrary code execution in the context of the current user.
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< 2020.7>= 2022, < 2022.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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 installed Adobe Framemaker versionOpen Adobe Framemaker, go to Help > About Adobe Framemaker to view the exact version number, or check the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Framemaker\VersionAffected if Version shown is 2020.6 or earlier, OR is 2022.0 through 2022.4 (i.e., falls in < 2020.7 or >= 2022 and < 2022.5)
-
Check for user-accessible file import or upload functionalityLook for features that allow importing files into Framemaker documents, such as XML/JSON import, image insertion, or document merge features accessible to end usersAffected if File upload or import features are available to users without additional validation
-
Inspect upload directories for suspicious file typesCheck default working directories (e.g., Documents\Adobe\Framemaker, Temp folders) for newly created or modified files with extensions such as .exe, .dll, .bat, .ps1, .vbs, .js, or other scriptable file types that were not intentionally placed thereAffected if Unexpected executable or script files are present in Framemaker working directories
-
Review application logs for file processing eventsCheck Framemaker log files (typically in %APPDATA%\Adobe\Framemaker\logs or Windows Event Viewer for application errors) for entries indicating automated processing of uploaded filesAffected if Logs show processing of file types that should require user confirmation or that originate from untrusted locations
You are affected if Adobe Framemaker version is 2020.6 or earlier, or between 2022.0 and 2022.4 inclusive, and users have access to file upload or import functionality that processes files without validating type.
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 · scoped2020.72022.5
Apply available vendor patches for Adobe Framemaker to address this vulnerability. Until patched, implement file type validation and content inspection on any file upload functionality, restrict file execution permissions, and educate users about the risks of opening untrusted files.
Adobe Framemaker 2020.7 or Adobe Framemaker 2022.5 (or subsequent releases)
- 1. Check current Adobe Framemaker version: Launch Framemaker > Help > About Adobe Framemaker
- 2. If version is 2020.6 or earlier, or 2022.0-2022.4, the system is vulnerable
- 3. Download Adobe Framemaker 2020.7 (for 2020.x users) or 2022.5 or later (for 2022.x users) from the official Adobe website: https://helpx.adobe.com/framemaker/download.html
- 4. Close all running instances of Adobe Framemaker
- 5. Back up any critical documents and settings before updating
- 6. Run the downloaded installer with administrator privileges
- 7. Follow the on-screen installation prompts to complete the update
- 8. After installation, verify the version via Help > About Adobe Framemaker confirms 2020.7 or 2022.5+
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47423 — 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-2024-47423 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