{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-28485 exists.","fix":"No fix has been published for CVE-2023-28485 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-28485 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-28485 and fix it if it is affected.\n\nWhat it is: CVE-2023-28485 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jun 2023. Any signed-in user can exploit it over the network, 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-2023-28485 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-2023-28485/ (Markdown: https://insights.sbomify.com/CVE-2023-28485/index.md)","id":"CVE-2023-28485","markdown":"https://insights.sbomify.com/CVE-2023-28485/index.md","name":"CVE-2023-28485","record":{"aliases":["GHSA-69jw-68vm-vprw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WeKan project management","requires_auth":"low_privilege","summary":"Authenticated users can inject arbitrary scripts via file attachment names in WeKan, potentially leading to code execution or account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wekan","vendor":"wekan_project"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"A stored cross-site scripting (Stored XSS) vulnerability in file preview in WeKan before 6.75 allows remote authenticated users to inject arbitrary web script or HTML via names of file attachments. Any user can obtain the privilege to rename within their own board (where they have BoardAdmin access), and renameAttachment does not block XSS payloads.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2023-28485","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Other in n/a","id":"CVE-2023-28486"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2023-28484"},"products":["n/a"],"published":"2023-06-26","related":[{"cvss_score":9.3,"headline":"Wekan has Cross-Board IDOR in Custom Fields Update Endpoints","id":"CVE-2026-30843","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":9.3,"headline":"Wekan Vulnerable to SSRF through Lack of Validation or Filtering in Attachment URL Loading","id":"CVE-2026-30844","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":9.3,"headline":"Wekan Credential Leak via notificationUsers Publication Exposes Password Hashes and Session Tokens","id":"CVE-2026-30847","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2025-65780","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":8.7,"headline":"Wekan Exposes All Global Webhook Integrations through globalwebhooks Publication","id":"CVE-2026-30846","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.7,"headline":"WeKan \u003c 8.19 LDAP Authentication Filter Injection","id":"CVE-2026-25560","kev_date_added":null,"published":"2026-02-07"},{"cvss_score":8.2,"headline":"Denial of service in n/a","id":"CVE-2025-65781","kev_date_added":null,"published":"2025-12-15"}],"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":"2024-12-04","vendors":["n/a"]},"summary":"Authenticated users can inject arbitrary scripts via file attachment names in WeKan, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2023-28485/"}