{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-8152 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8152 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8152 is a medium-severity missing authorization vulnerability in blendmedia WP CTA – Call Now Button, Sticky Button \u0026 Call to Action Builder, published on 2 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8152 and fix it if it is affected.\n\nWhat it is: CVE-2025-8152 is a medium-severity missing authorization vulnerability in blendmedia WP CTA – Call Now Button, Sticky Button \u0026 Call to Action Builder, published on 2 Aug 2025. 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-2025-8152 in the wild and no public exploit code.\n\nAffected product: blendmedia WP CTA – Call Now Button, Sticky Button \u0026 Call to Action Builder. 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-2025-8152/ (Markdown: https://insights.sbomify.com/CVE-2025-8152/index.md)","id":"CVE-2025-8152","markdown":"https://insights.sbomify.com/CVE-2025-8152/index.md","name":"CVE-2025-8152","record":{"aliases":["GHSA-vrcj-8r35-5gqx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can modify sticky CTA status and names due to missing capability checks in the WP CTA WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The WP CTA – Call To Action Plugin, Sticky CTA, Sticky Buttons plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'update_cta_status' and 'change_sticky_sidebar_name' functions in all versions up to, and including, 1.7.0. This makes it possible for unauthenticated attackers to update the status of a sticky and update the name displayed in the back-end WP CTA Dashboard.","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":"Missing authorization in WP CTA – Call Now Button, Sticky Button \u0026 Call to Action Builder","id":"CVE-2025-8152","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in UNIVERGE IX","id":"CVE-2025-8153"},"packages":[],"prev":{"headline":"Path traversal in HT Mega Addons for Elementor – Elementor Widgets \u0026 Template Builder","id":"CVE-2025-8151"},"products":["WP CTA – Call Now Button, Sticky Button \u0026 Call to Action Builder"],"published":"2025-08-02","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-04-08","vendors":["blendmedia"]},"summary":"Unauthenticated attackers can modify sticky CTA status and names due to missing capability checks in the WP CTA WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-8152/"}