CVE-2014-9677
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 · uneditedCross-site scripting (XSS) vulnerability in FlexPaperViewer.swf in Flexpaper before 2.3.1 allows remote attackers to inject arbitrary web script or HTML via the Swfile parameter.
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 confidenceCross-site scripting (XSS) vulnerability in FlexPaperViewer.swf allows remote attackers to inject arbitrary web script or HTML via the Swfile parameter. The Swfile parameter is reflected without proper sanitization, enabling script execution in the context of the user's browser.
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<= 2.3.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Locate FlexPaperViewer.swf on the systemSearch web-accessible directories for the file FlexPaperViewer.swf. Common paths include /js/, /flexpaper/, /viewer/, or application web roots. Use commands like: find /var/www -name "FlexPaperViewer.swf" 2>/dev/null (Linux) ordir /s /b C:\*FlexPaperViewer.swf (Windows)Affected if The file FlexPaperViewer.swf exists in a web-accessible directory
-
Identify the FlexPaper versionCheck for version information in accompanying files such as README, CHANGELOG, version.js, or the SWF file itself. Also check the application's documentation or the web page loading the SWF for version indicators.Affected if The installed version is 2.3.0 or lower, or version information cannot be verified and FlexPaperViewer.swf is present
-
Verify the Swfile parameter is in useInspect the HTML pages that embed FlexPaperViewer.swf for the 'Swfile' parameter. Search source code for <param name="movie" value="FlexPaperViewer.swf"> or similar SWF embedding code, and check for Swfile parameter declarations.Affected if The Swfile parameter is present in the SWF embedding code and is used to load PDF or document files
-
Confirm parameter reflection without sanitizationTest the deployed application by requesting the FlexPaperViewer.swf with a crafted Swfile parameter containing script tags (e.g., ?Swfile=test.pdf"><script>alert(1)</script>). Monitor if the parameter value is reflected unescaped in the response.Affected if The Swfile parameter value is reflected in the HTML/SWF response without HTML encoding or sanitization
The environment is affected if FlexPaperViewer.swf version 2.3.0 or lower is present and the Swfile parameter is processed without sanitization, allowing reflected XSS.
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.
From vendor dataUpgrade FlexPaper to version 2.3.1 or later which contains the patched SWF file, or implement input validation/sanitization on the Swfile parameter before processing.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9677 — 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-2014-9677 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