{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-0627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0627 is a medium-severity cross-site scripting vulnerability in hiroaki-miyashita Custom Field Template, published on 11 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-0627 and fix it if it is affected.\n\nWhat it is: CVE-2024-0627 is a medium-severity cross-site scripting vulnerability in hiroaki-miyashita Custom Field Template, published on 11 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-0627 in the wild and no public exploit code.\n\nAffected product: hiroaki-miyashita Custom Field Template. 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-2024-0627/ (Markdown: https://insights.sbomify.com/CVE-2024-0627/index.md)","id":"CVE-2024-0627","markdown":"https://insights.sbomify.com/CVE-2024-0627/index.md","name":"CVE-2024-0627","record":{"aliases":["GHSA-prm3-v4r8-g2mv"],"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 attackers can inject arbitrary scripts via custom field names, leading to stored XSS execution for other users.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"custom_field_template","vendor":"wpgogo"}],"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 Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's custom field name column in all versions up to, and including, 2.6.1 due to insufficient input sanitization and output escaping on user supplied custom fields. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.","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":"Custom Field Template \u003c= 2.6.1 - Authenticated(Constibutor+) Stored Cross-Site Scripting via Custom Field Name","id":"CVE-2024-0627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Server-side request forgery in WP RSS Aggregator – RSS Import, News Feeds, Feed to Post, and Autoblogging","id":"CVE-2024-0628"},"packages":[],"prev":{"headline":"WooCommerce Clover Payment Gateway \u003c= 1.3.1 - Missing Authorization via callback_handler","id":"CVE-2024-0626"},"products":["Custom Field Template"],"published":"2024-06-11","related":[{"cvss_score":7.2,"headline":"Custom Field Template \u003c 2.5.8 - Admin+ PHP Object Injection","id":"CVE-2022-4324","kev_date_added":null,"published":"2023-01-02"},{"cvss_score":7.1,"headline":"WordPress Custom Field Template Plugin \u003c= 2.5.9 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-38392","kev_date_added":null,"published":"2023-08-07"},{"cvss_score":6.5,"headline":"WordPress Custom Field Template plugin \u003c= 2.6.5 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-44062","kev_date_added":null,"published":"2024-09-15"},{"cvss_score":6.4,"headline":"Custom Field Template \u003c= 2.6.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via shortcode","id":"CVE-2023-6745","kev_date_added":null,"published":"2024-06-11"},{"cvss_score":4.4,"headline":"Custom Field Template \u003c= 2.6.1 - Authenticated (Admin+) Stored Cross-Site Scritping","id":"CVE-2024-0653","kev_date_added":null,"published":"2024-06-11"},{"cvss_score":4.3,"headline":"Custom Field Template \u003c= 2.6.1 - Authenticated(Contributor+) Information Exposure","id":"CVE-2023-6748","kev_date_added":null,"published":"2024-06-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-04-08","vendors":["hiroaki-miyashita"]},"summary":"Authenticated attackers can inject arbitrary scripts via custom field names, leading to stored XSS execution for other users.","url":"https://insights.sbomify.com/CVE-2024-0627/"}