{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3546 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3546 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3546 is a medium-severity missing authorization vulnerability in forfront e-shot, published on 21 Mar 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-3546 and fix it if it is affected.\n\nWhat it is: CVE-2026-3546 is a medium-severity missing authorization vulnerability in forfront e-shot, published on 21 Mar 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-3546 in the wild and no public exploit code.\n\nAffected product: forfront e-shot. 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-3546/ (Markdown: https://insights.sbomify.com/CVE-2026-3546/index.md)","id":"CVE-2026-3546","markdown":"https://insights.sbomify.com/CVE-2026-3546/index.md","name":"CVE-2026-3546","record":{"aliases":["GHSA-7m85-p686-23rm"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Authenticated attackers can exploit missing authorization checks to extract sensitive API tokens and subaccount data from the e-shot 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:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-202","name":"Exposure of Sensitive Information Through Data Queries"}],"description":"The e-shot form builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.2. The eshot_form_builder_get_account_data() function is registered as a wp_ajax_ AJAX handler accessible to all authenticated users. The function lacks any capability check (e.g., current_user_can('manage_options')) and does not verify a nonce. It directly queries the database for the e-shot API token stored in the eshotformbuilder_control table and returns it along with all subaccount data as a JSON response. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract the e-shot API token and subaccount information, which could then be used to access the victim's e-shot platform account.","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 e-shot","id":"CVE-2026-3546","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"wolfSSL: out-of-bounds read (DoS) in ALPN parsing due to incomplete validation","id":"CVE-2026-3547"},"packages":[],"prev":{"headline":"Other in Chrome","id":"CVE-2026-3545"},"products":["e-shot"],"published":"2026-03-21","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":["forfront"]},"summary":"Authenticated attackers can exploit missing authorization checks to extract sensitive API tokens and subaccount data from the e-shot WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-3546/"}