{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24129 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24129 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24129 is a medium-severity cross-site scripting vulnerability in Unknown Themify Portfolio Post, published on 18 Mar 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-24129 and fix it if it is affected.\n\nWhat it is: CVE-2021-24129 is a medium-severity cross-site scripting vulnerability in Unknown Themify Portfolio Post, published on 18 Mar 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-24129 in the wild and no public exploit code.\n\nAffected product: Unknown Themify Portfolio Post. 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-2021-24129/ (Markdown: https://insights.sbomify.com/CVE-2021-24129/index.md)","id":"CVE-2021-24129","markdown":"https://insights.sbomify.com/CVE-2021-24129/index.md","name":"CVE-2021-24129","record":{"aliases":["GHSA-mv99-79gw-2g8g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Low-privileged users can inject malicious scripts into posts, potentially leading to privilege escalation in the Themify Portfolio Post plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"portfolio_post","vendor":"themify"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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":"Unvalidated input and lack of output encoding in the Themify Portfolio Post WordPress plugin, versions before 1.1.6, lead to Stored Cross-Site Scripting (XSS) vulnerabilities allowing low-privileged users (Contributor+) to inject arbitrary JavaScript code or HTML in posts where the Themify Custom Panel is embedded, which could lead to privilege escalation.","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":"Themify Portfolio Post \u003c 1.1.6 - Authenticated Stored Cross-Site Scripting","id":"CVE-2021-24129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"WP Google Map Plugin \u003c 4.1.5 - Authenticated SQL Injection","id":"CVE-2021-24130"},"packages":[],"prev":{"headline":"Team Members \u003c 5.0.4 - Authenticated Stored Cross-Site Scripting (XSS)","id":"CVE-2021-24128"},"products":["Themify Portfolio Post"],"published":"2021-03-18","related":[{"cvss_score":5.4,"headline":"Themify Portfolio Post \u003c 1.2.2 - Contributor+ Stored XSS","id":"CVE-2023-0362","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":5.4,"headline":"Themify Portfolio Post \u003c 1.2.1 - Contributor+ Stored XSS","id":"CVE-2022-4464","kev_date_added":null,"published":"2023-01-16"},{"cvss_score":5.4,"headline":"Themify Portfolio Post \u003c 1.1.7 - Reflected Cross-Site Scripting","id":"CVE-2022-0200","kev_date_added":null,"published":"2022-02-14"},{"cvss_score":4.1,"headline":"WordPress Themify Portfolio Post Plugin \u003c= 1.2.4 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2022-32970","kev_date_added":null,"published":"2023-05-10"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Low-privileged users can inject malicious scripts into posts, potentially leading to privilege escalation in the Themify Portfolio Post plugin.","url":"https://insights.sbomify.com/CVE-2021-24129/"}