{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-18059 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18059 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18059 is a medium-severity vulnerability in PixelYourSite Pro – Your smart PIXEL (TAG) Manager, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18059 and fix it if it is affected.\n\nWhat it is: CVE-2026-18059 is a medium-severity vulnerability in PixelYourSite Pro – Your smart PIXEL (TAG) Manager, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-18059 in the wild and no public exploit code.\n\nAffected product: PixelYourSite Pro – Your smart PIXEL (TAG) Manager. 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-18059/ (Markdown: https://insights.sbomify.com/CVE-2026-18059/index.md)","id":"CVE-2026-18059","markdown":"https://insights.sbomify.com/CVE-2026-18059/index.md","name":"CVE-2026-18059","record":{"aliases":["GHSA-xf2j-qr39-56f9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract sensitive WooCommerce purchase metadata by accessing the order-received endpoint with invalid keys.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The PixelYourSite – Your smart PIXEL (TAG) \u0026 API Manager plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 11.2.1 via the getWooPurchaseEventParams. This makes it possible for unauthenticated attackers to extract WooCommerce purchase metadata — including product names, product IDs, quantities, per-item prices, order totals, currency, and order/transaction IDs — for any existing order by supplying an invalid or arbitrary order key. This is exploitable against any known or enumerated order ID, as the plugin resolves the order from the URL path variable alone and emits the full woo_purchase tracking payload into the page HTML via the pysOptions JavaScript object across its Facebook, Google Analytics, and Google Tag Manager integrations regardless of key validity.","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":"Information disclosure in PixelYourSite Pro – Your smart PIXEL (TAG) Manager","id":"CVE-2026-18059","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":12,"next":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2026-18060"},"packages":[],"prev":{"headline":"Missing authorization in Smart Connect Application","id":"CVE-2026-18058"},"products":["PixelYourSite Pro – Your smart PIXEL (TAG) Manager","PixelYourSite – Your smart PIXEL (TAG) \u0026 API Manager"],"published":"2026-08-01","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["pixelyoursite"]},"summary":"Unauthenticated attackers can extract sensitive WooCommerce purchase metadata by accessing the order-received endpoint with invalid keys.","url":"https://insights.sbomify.com/CVE-2026-18059/"}