CVE-2025-49341
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 Request Forgery (CSRF) vulnerability in Alex Furr PDF Creator Lite pdf-creator-lite allows Stored XSS.This issue affects PDF Creator Lite: from n/a through <= 1.2.
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 confidenceA CSRF vulnerability in PDF Creator Lite enables attackers to craft malicious requests that inject and store XSS payloads in the application. An attacker would need to trick an authenticated user into visiting a malicious page, causing the browser to automatically submit a request that stores the XSS payload, which then executes when other users view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 PDF Creator Lite installation and versionLocate the application installation directory and check for version information in metadata files (e.g., package.json, VERSION file, or application settings panel). Compare the installed version against any known version releases of PDF Creator Lite.Affected if The installed version is older than the patched version and falls within the affected range.
-
Verify authentication is required for vulnerable operationsConfirm that the application requires user authentication before performing state-changing operations such as creating, editing, or storing PDF-related content.Affected if The application allows unauthenticated users to submit requests that store content, indicating the CSRF protection gap is exploitable.
-
Inspect stored content rendering mechanismsExamine how the application displays user-submitted content to other users (e.g., PDF previews, comments, document titles, metadata fields). Check if output encoding is applied when rendering stored content in HTML pages.Affected if Stored content is rendered without proper output encoding, allowing injected scripts to execute in other users' browsers.
-
Check for anti-CSRF token implementationReview the application's forms and API endpoints that perform state-changing operations. Verify that each includes and validates a unique anti-CSRF token per request.Affected if State-changing endpoints lack anti-CSRF token validation, enabling cross-site request forgery attacks.
-
Review input validation on storage endpointsAnalyze the server-side code handling requests that store content. Determine if input validation filters or sanitizes special characters before storage.Affected if Input validation is absent or insufficient, permitting malicious scripts to be stored as payload.
A user is affected if PDF Creator Lite is running a version without anti-CSRF protection and without input validation or output encoding, allowing stored XSS to execute when users view the injected content.
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 dataImplement anti-CSRF tokens on all state-changing operations and apply proper input validation and output encoding to prevent XSS injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49341 — 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-2025-49341 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