{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-115734 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-115734 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-115734 is a critical path traversal vulnerability in Pay with a tweet, published on 11 Nov 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-115734 and fix it if it is affected.\n\nWhat it is: CVE-2026-115734 is a critical path traversal vulnerability in Pay with a tweet, published on 11 Nov 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-115734 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: Pay with a tweet. 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-115734/ (Markdown: https://insights.sbomify.com/CVE-2026-115734/index.md)","id":"CVE-2026-115734","markdown":"https://insights.sbomify.com/CVE-2026-115734/index.md","name":"CVE-2026-115734","record":{"aliases":["GHSA-pwpg-m6pr-8g76"],"analysis":{"component_type":"cms_plugin","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","requires_specific_call":false,"summary":"Subscriber-level users can delete arbitrary server files via the Pay with a tweet plugin, potentially compromising the site.","user_interaction":"not_required","vuln_class":"path_traversal","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"WPScan","component":null,"cpe":[],"cvss":{"score":9.6,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"The Pay with a tweet WordPress plugin through 1.0.5 does not validate a file path before deleting it, nor does it restrict access to the relevant administration screens, allowing users with a role as low as Subscriber to delete arbitrary files on the server, which can lead to a full site compromise.","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":"Pay With a Tweet \u003c= 1.0.5 - Subscriber+ Arbitrary File Deletion via Button Download Path","id":"CVE-2026-115734","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Somatic Framework \u003c= 1.8.14 - Subscriber+ Arbitrary File Deletion","id":"CVE-2026-115735"},"nickname":null,"packages":[],"prev":{"headline":"PrintAura WooCommerce API \u003c= 4.0.2 - Unauthenticated WooCommerce REST API Authentication Bypass","id":"CVE-2026-115733"},"products":["Pay with a tweet"],"published":"2026-11-11","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","text_fixes":[],"updated":"2026-11-11","vendor_status":[],"vendors":[]},"summary":"Subscriber-level users can delete arbitrary server files via the Pay with a tweet plugin, potentially compromising the site.","url":"https://insights.sbomify.com/CVE-2026-115734/"}