{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61549 exists.","fix":"No fix has been published for CVE-2025-61549 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61549 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-61549 and fix it if it is affected.\n\nWhat it is: CVE-2025-61549 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61549 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-61549/ (Markdown: https://insights.sbomify.com/CVE-2025-61549/index.md)","id":"CVE-2025-61549","markdown":"https://insights.sbomify.com/CVE-2025-61549/index.md","name":"CVE-2025-61549","record":{"aliases":["GHSA-xp5p-5cr9-v76h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Print Shop Pro WebDesk","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript in victim browsers via unsanitized LoginID input in Print Shop Pro WebDesk, potentially leading to session hijacking.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"print_shop_pro_webdesk","vendor":"edubusinesssolutions"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Cross-Site Scripting (XSS) is present on the LoginID parameter on the /PSP/app/web/reg/reg_display.asp endpoint in edu Business Solutions Print Shop Pro WebDesk version 18.34 (fixed in 19.76). Unsanitized user input is reflected in HTTP responses without proper HTML encoding or escaping. This allows attackers to execute arbitrary JavaScript in the context of a victim s browser session","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2025-61549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-61550"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-61548"},"products":["n/a"],"published":"2026-01-08","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2026-26725","kev_date_added":null,"published":"2026-02-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-61548","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":9.1,"headline":"Business logic in n/a","id":"CVE-2025-61546","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-61547","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2025-61550","kev_date_added":null,"published":"2026-01-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-10","vendors":["n/a"]},"summary":"Attackers can execute arbitrary JavaScript in victim browsers via unsanitized LoginID input in Print Shop Pro WebDesk, potentially leading to session hijacking.","url":"https://insights.sbomify.com/CVE-2025-61549/"}