{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-42556 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-42556 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42556 is a high-severity cross-site scripting vulnerability in gitroomhq postiz-app, published on 8 May 2026. 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-2026-42556 and fix it if it is affected.\n\nWhat it is: CVE-2026-42556 is a high-severity cross-site scripting vulnerability in gitroomhq postiz-app, published on 8 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-42556 in the wild and no public exploit code.\n\nAffected product: gitroomhq postiz-app. 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-2026-42556/ (Markdown: https://insights.sbomify.com/CVE-2026-42556/index.md)","id":"CVE-2026-42556","markdown":"https://insights.sbomify.com/CVE-2026-42556/index.md","name":"CVE-2026-42556","record":{"aliases":["GHSA-hhxq-3wg7-4rj8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Social media scheduling tool","requires_auth":"low_privilege","summary":"Authenticated users can inject malicious HTML into post previews, leading to stored XSS and potential account takeover when victims view the link.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"postiz","vendor":"gitroom"}],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Postiz is an AI social media scheduling tool. From version 2.21.6 to before version 2.21.7, any authenticated user who can create a post can store arbitrary HTML in post content by tampering their own save request and send the public preview link /p/\u003cpostId\u003e?share=true to another user. The preview page renders that stored HTML with dangerouslySetInnerHTML on the main application origin. This issue has been patched in version 2.21.7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Postiz stored XSS in public preview page","id":"CVE-2026-42556","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"jupyterlab: Command linker attributes in HTML enable one-click command execution from untrusted content","id":"CVE-2026-42557"},"packages":[],"prev":{"headline":"Valtimo: SpEL injection via StandardEvaluationContext allows Remote Code Execution by admin users","id":"CVE-2026-42555"},"products":["postiz-app"],"published":"2026-05-08","related":[{"cvss_score":10,"headline":"Postiz: Arbitrary Code Execution and Token Exfiltration in pr-docker-build.yml via untrusted Dockerfile.dev","id":"CVE-2026-42298","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":8.9,"headline":"Postiz Has Unrestricted File Upload via MIME Type Spoofing that Leads to Stored XSS","id":"CVE-2026-40487","kev_date_added":null,"published":"2026-04-18"},{"cvss_score":8.6,"headline":"Postiz: Unauthenticated Full-Read SSRF via /public/stream Endpoint with Trivially Bypassable Extension Check","id":"CVE-2026-34577","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":8.3,"headline":"Postiz: SSRF in upload-from-url endpoint allows fetching internal resources and cloud metadata","id":"CVE-2026-34576","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":8.2,"headline":"Postiz has Server-Side Request Forgery via Redirect Bypass in /api/public/stream","id":"CVE-2026-40168","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":5.4,"headline":"Postiz: SSRF via Webhook Creation Endpoint Missing URL Safety Validation","id":"CVE-2026-34590","kev_date_added":null,"published":"2026-04-02"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["gitroomhq"]},"summary":"Authenticated users can inject malicious HTML into post previews, leading to stored XSS and potential account takeover when victims view the link.","url":"https://insights.sbomify.com/CVE-2026-42556/"}