{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24826 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24826 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24826 is a medium-severity cross-site scripting vulnerability in Unknown Custom Content Shortcode, published on 7 Mar 2022. 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-24826 and fix it if it is affected.\n\nWhat it is: CVE-2021-24826 is a medium-severity cross-site scripting vulnerability in Unknown Custom Content Shortcode, published on 7 Mar 2022. 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-24826 in the wild and no public exploit code.\n\nAffected product: Unknown Custom Content Shortcode. 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-24826/ (Markdown: https://insights.sbomify.com/CVE-2021-24826/index.md)","id":"CVE-2021-24826","markdown":"https://insights.sbomify.com/CVE-2021-24826/index.md","name":"CVE-2021-24826","record":{"aliases":["GHSA-h77p-7f34-7fqv"],"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 users can inject malicious scripts via unescaped custom fields, allowing code execution in the context of other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"custom_content_shortcode","vendor":"custom_content_shortcode_project"}],"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":"The Custom Content Shortcode WordPress plugin before 4.0.2 does not escape custom fields before outputting them, which could allow Contributor+ (v \u003c 4.0.1) or Admin+ (v \u003c 4.0.2) users to perform Cross-Site Scripting attacks even when the unfiltered_html is disallowed. Please note that such attack is still possible by admin+ in single site blogs by default (but won't be when the unfiltered_html is disallowed)","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 Content Shortcode \u003c 4.0.2 - Authenticated Stored Cross-Site Scripting","id":"CVE-2021-24826","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Asgaros Forum \u003c 1.15.13 - Unauthenticated SQL Injection","id":"CVE-2021-24827"},"packages":[],"prev":{"headline":"Custom Content Shortcode \u003c 4.0.2 - Authenticated Arbitrary File Access / LFI","id":"CVE-2021-24825"},"products":["Custom Content Shortcode"],"published":"2022-03-07","related":[{"cvss_score":8.8,"headline":"Custom Content Shortcode \u003c= 4.0.2 - Contributor+ LFI","id":"CVE-2023-0340","kev_date_added":null,"published":"2023-03-20"},{"cvss_score":5.4,"headline":"Custom Content Shortcode \u003c= 4.0.2 - Contributor+ Stored XSS","id":"CVE-2023-0273","kev_date_added":null,"published":"2023-03-20"},{"cvss_score":4.3,"headline":"Custom Content Shortcode \u003c 4.0.1 - Unauthorised Arbitrary Post Metadata Access","id":"CVE-2021-24824","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":4.3,"headline":"Custom Content Shortcode \u003c 4.0.2 - Authenticated Arbitrary File Access / LFI","id":"CVE-2021-24825","kev_date_added":null,"published":"2022-03-07"}],"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":"Authenticated users can inject malicious scripts via unescaped custom fields, allowing code execution in the context of other users.","url":"https://insights.sbomify.com/CVE-2021-24826/"}