{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4464 exists.","fix":"No fix has been published for CVE-2022-4464 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4464 is a medium-severity cross-site scripting vulnerability in Unknown Themify Portfolio Post, published on 16 Jan 2023. 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-2022-4464 and fix it if it is affected.\n\nWhat it is: CVE-2022-4464 is a medium-severity cross-site scripting vulnerability in Unknown Themify Portfolio Post, published on 16 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4464 exists.\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-2022-4464/ (Markdown: https://insights.sbomify.com/CVE-2022-4464/index.md)","id":"CVE-2022-4464","markdown":"https://insights.sbomify.com/CVE-2022-4464/index.md","name":"CVE-2022-4464","record":{"aliases":["GHSA-237f-7hfc-5r9q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Contributors can inject malicious scripts via shortcode attributes, potentially compromising admin accounts in Themify Portfolio Post.","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":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"Themify Portfolio Post WordPress plugin before 1.2.1 does not validate and escapes some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as a contributor to perform Stored Cross-Site Scripting attacks, which could be used against high privileged users such as admin.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Themify Portfolio Post \u003c 1.2.1 - Contributor+ Stored XSS","id":"CVE-2022-4464","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"WP Video Lightbox \u003c 1.9.7 - Contributor+ Stored XSS","id":"CVE-2022-4465"},"packages":[],"prev":{"headline":"This candidate is unused by its CNA.","id":"CVE-2022-4463"},"products":["Themify Portfolio Post"],"published":"2023-01-16","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.1.7 - Reflected Cross-Site Scripting","id":"CVE-2022-0200","kev_date_added":null,"published":"2022-02-14"},{"cvss_score":5.4,"headline":"Themify Portfolio Post \u003c 1.1.6 - Authenticated Stored Cross-Site Scripting","id":"CVE-2021-24129","kev_date_added":null,"published":"2021-03-18"},{"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-08","vendors":["Unknown"]},"summary":"Contributors can inject malicious scripts via shortcode attributes, potentially compromising admin accounts in Themify Portfolio Post.","url":"https://insights.sbomify.com/CVE-2022-4464/"}