{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-29099 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-29099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-29099 is a high-severity cross-site scripting vulnerability in Evergreen Content Poster, published on 19 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-29099 and fix it if it is affected.\n\nWhat it is: CVE-2024-29099 is a high-severity cross-site scripting vulnerability in Evergreen Content Poster, published on 19 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-29099 in the wild and no public exploit code.\n\nAffected product: Evergreen Content Poster. 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-29099/ (Markdown: https://insights.sbomify.com/CVE-2024-29099/index.md)","id":"CVE-2024-29099","markdown":"https://insights.sbomify.com/CVE-2024-29099/index.md","name":"CVE-2024-29099","record":{"aliases":["GHSA-34h5-53fh-qqxm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in victim browsers via reflected XSS in the Evergreen Content Poster WordPress plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"evergreen_content_poster","vendor":"evergreencontentposter"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Evergreen Content Poster allows Reflected XSS.This issue affects Evergreen Content Poster: from n/a through 1.4.1.","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":"WordPress Evergreen Content Poster plugin \u003c= 1.4.1 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-29099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress AI Engine plugin \u003c= 2.1.4 - Arbitrary File Upload vulnerability","id":"CVE-2024-29100"},"packages":[],"prev":{"headline":"WordPress WP Calameo plugin \u003c= 2.1.7 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-29098"},"products":["Evergreen Content Poster"],"published":"2024-03-19","related":[{"cvss_score":5.9,"headline":"WordPress Evergreen Content Poster Plugin \u003c= 1.3.6.1 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-41127","kev_date_added":null,"published":"2023-11-30"},{"cvss_score":5.4,"headline":"WordPress Evergreen Content Poster plugin \u003c= 1.4.2 - Broken Access Control vulnerability","id":"CVE-2024-32824","kev_date_added":null,"published":"2024-06-09"},{"cvss_score":5.3,"headline":"Missing authorization in Evergreen Content Poster – Auto Post and Schedule Your Best Content to Social Media","id":"CVE-2024-12071","kev_date_added":null,"published":"2025-01-18"}],"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-28","vendors":["Evergreen Content Poster"]},"summary":"Attackers can execute arbitrary scripts in victim browsers via reflected XSS in the Evergreen Content Poster WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-29099/"}