{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-13295 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13295 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-13295 is a medium-severity cross-site scripting vulnerability in gpriday Page Builder by SiteOrigin, published on 27 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-13295 and fix it if it is affected.\n\nWhat it is: CVE-2026-13295 is a medium-severity cross-site scripting vulnerability in gpriday Page Builder by SiteOrigin, published on 27 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-13295 in the wild and no public exploit code.\n\nAffected product: gpriday Page Builder by SiteOrigin. 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-13295/ (Markdown: https://insights.sbomify.com/CVE-2026-13295/index.md)","id":"CVE-2026-13295","markdown":"https://insights.sbomify.com/CVE-2026-13295/index.md","name":"CVE-2026-13295","record":{"aliases":["GHSA-qq5h-jpgc-p42f"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can inject arbitrary scripts via the panels_data parameter, leading to stored XSS execution on frontend pages.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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":"The Page Builder by SiteOrigin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via panels_data Parameter in all versions up to, and including, 2.34.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because the nonce and edit_post capability checks enforced during save are both satisfied by Contributor-level users for their own posts, and the panels_data value is stored as post meta — outside the scope of WordPress's unfiltered_html carve-out — meaning no wp_kses fallback prevents the unsanitized WP_Widget_Custom_HTML content from being persisted and later rendered verbatim on the frontend.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in Page Builder by SiteOrigin","id":"CVE-2026-13295","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Security vulnerabilities have been addressed in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-13297"},"packages":[],"prev":{"headline":"IBM MQ Java messaging is vulnerable to remote code execution","id":"CVE-2026-13293"},"products":["Page Builder by SiteOrigin"],"published":"2026-06-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-06-29","vendors":["gpriday"]},"summary":"Authenticated contributors can inject arbitrary scripts via the panels_data parameter, leading to stored XSS execution on frontend pages.","url":"https://insights.sbomify.com/CVE-2026-13295/"}