CVE-2013-5325
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 Reader and Acrobat 11.x before 11.0.05 on Windows allow remote attackers to execute arbitrary JavaScript code in a javascript: URL via a crafted PDF document.
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 confidenceThis vulnerability allows remote attackers to execute arbitrary JavaScript code via specially crafted PDF documents containing javascript: URLs. The flaw exists in Adobe Reader and Acrobat 11.x versions prior to 11.0.05 on Windows, where the application fails to properly sanitize javascript: URLs embedded in PDF files, enabling script execution in the context of the application.
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= 11.0= 11.0.1= 11.0.2= 11.0.3= 11.0.4= 11.0= 11.0.1= 11.0.2= 11.0.3= 11.0.4CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 productOpen Adobe Reader or Acrobat, then go to Help > About (or check Add/Remove Programs in Windows Control Panel) to see the exact version numberAffected if The product is Adobe Reader or Acrobat version 11.0, 11.0.1, 11.0.2, 11.0.3, or 11.0.4 on Windows
-
Verify the exact version against affected listCompare the installed version number to the vulnerable versions: 11.0, 11.0.1, 11.0.2, 11.0.3, and 11.0.4. Version 11.0.05 or later is not affectedAffected if The installed version is exactly 11.0, 11.0.1, 11.0.2, 11.0.3, or 11.0.4
-
Check if JavaScript is enabled in Adobe settingsIn Adobe Reader/Acrobat, go to Edit > Preferences > JavaScript and verify whether 'Enable Adobe JavaScript' is checkedAffected if JavaScript is enabled in the application preferences (the vulnerability requires JavaScript to be active to exploit the javascript: URL flaw)
You are affected if Adobe Reader or Acrobat version 11.0 through 11.0.4 is installed on Windows AND JavaScript is enabled in the application settings.
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 Reader and Acrobat to version 11.0.05 or later. Additionally, disable JavaScript execution in Adobe Reader/Acrobat settings if not required, and implement network-level controls to block PDF files from untrusted sources.
Adobe Acrobat/Acrobat Reader 11.0.05 or later
- Download Adobe Acrobat or Acrobat Reader version 11.0.05 or later from the official Adobe website
- Install the updated version on Windows systems
- Verify the installation by checking Help > About Adobe Acrobat/Reader to confirm the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5325 — 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-2013-5325 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