{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-4779 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4779 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4779 is a medium-severity cross-site scripting vulnerability in specialk User Submitted Posts – Enable Users to Submit Posts from the Front End, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-4779 and fix it if it is affected.\n\nWhat it is: CVE-2023-4779 is a medium-severity cross-site scripting vulnerability in specialk User Submitted Posts – Enable Users to Submit Posts from the Front End, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-4779 in the wild and no public exploit code.\n\nAffected product: specialk User Submitted Posts – Enable Users to Submit Posts from the Front End. 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-2023-4779/ (Markdown: https://insights.sbomify.com/CVE-2023-4779/index.md)","id":"CVE-2023-4779","markdown":"https://insights.sbomify.com/CVE-2023-4779/index.md","name":"CVE-2023-4779","record":{"aliases":["GHSA-3c82-f6j3-5x2g"],"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 contributors can inject arbitrary scripts via shortcode attributes, leading to stored XSS execution on victim pages.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"user_submitted_posts","vendor":"plugin-planet"}],"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 User Submitted Posts plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's [usp_gallery] shortcode in versions up to, and including, 20230811 due to insufficient input sanitization and output escaping on user supplied attributes like 'before'. 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":"Cross-site scripting in User Submitted Posts – Enable Users to Submit Posts from the Front End","id":"CVE-2023-4779","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Heap-based Buffer Overflow in vim/vim","id":"CVE-2023-4781"},"packages":[],"prev":{"headline":"Out-of-bounds Read in gpac/gpac","id":"CVE-2023-4778"},"products":["User Submitted Posts – Enable Users to Submit Posts from the Front End"],"published":"2023-09-06","related":[{"cvss_score":9.8,"headline":"User Submitted Posts \u003c= 20190312 - Unauthenticated Arbitrary File Upload","id":"CVE-2019-25138","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":9,"headline":"WordPress User Submitted Posts Plugin \u003c= 20230902 is vulnerable to Arbitrary File Upload","id":"CVE-2023-45603","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":7.2,"headline":"User Submitted Posts \u003c= 20230809 - Unauthenticated Stored Cross-Site Scripting via 'user-submitted-content'","id":"CVE-2023-4308","kev_date_added":null,"published":"2023-08-15"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2016-11001","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":4.8,"headline":"User Submitted Posts \u003c 20240516 - Admin+ Stored XSS","id":"CVE-2024-5002","kev_date_added":null,"published":"2024-07-13"}],"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":["specialk"]},"summary":"Authenticated contributors can inject arbitrary scripts via shortcode attributes, leading to stored XSS execution on victim pages.","url":"https://insights.sbomify.com/CVE-2023-4779/"}