CVE-2025-46465
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 John Weissberg Print Science Designer print-science-designer allows Stored XSS.This issue affects Print Science Designer: from n/a through <= 1.3.155.
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 confidenceCSRF vulnerability in Print Science Designer allows attackers to trick authenticated users into submitting malicious requests that result in stored XSS payloads being persisted in the application. This affects all users who view the injected 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 Print Science Designer installationLocate the Print Science Designer application in your environment - check installed software listings, application directories, or web application manifests for 'Print Science Designer' or related componentsAffected if The application is not found in your environment
-
Determine installed versionQuery the application for its version information through the product's about panel, configuration files, or API endpoint that returns version metadataAffected if The installed version cannot be determined or is not documented to have fixed the CSRF vulnerability
-
Verify anti-CSRF protection existsInspect state-changing operations (form submissions, API POST/PUT/DELETE requests) for the presence of anti-CSRF tokens or SameSite cookie attributes. Capture a request and examine headers and body for token parametersAffected if State-changing operations lack anti-CSRF token validation or proper SameSite cookie settings
-
Check for stored XSS payloadsReview application databases, user-generated content storage, or configuration fields for suspicious script tags, event handlers, or javascript: URIs in stored dataAffected if Malicious scripts or XSS payloads are found persisted in application data
-
Review authentication session configurationExamine session cookies for SameSite and Secure attributes. Check if session tokens are validated on each state-changing requestAffected if Session cookies lack SameSite=Strict or SameSite=Lax attributes, or tokens are not validated per-request
Your environment is affected if Print Science Designer is present and state-changing operations lack anti-CSRF token validation, allowing stored XSS injection through authenticated user requests.
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 for state-changing operations and apply robust input validation with output encoding to prevent XSS injection.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46465 — 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-46465 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