{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24824 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24824 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24824 is a medium-severity missing authorization vulnerability in Unknown Custom Content Shortcode, published on 7 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-24824 and fix it if it is affected.\n\nWhat it is: CVE-2021-24824 is a medium-severity missing authorization vulnerability in Unknown Custom Content Shortcode, published on 7 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-24824 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-24824/ (Markdown: https://insights.sbomify.com/CVE-2021-24824/index.md)","id":"CVE-2021-24824","markdown":"https://insights.sbomify.com/CVE-2021-24824/index.md","name":"CVE-2021-24824","record":{"aliases":["GHSA-28mp-cx45-6mwq"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can access arbitrary post metadata, potentially exposing sensitive data like customer emails in WooCommerce.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"custom_content_shortcode","vendor":"custom_content_shortcode_project"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The [field] shortcode included with the Custom Content Shortcode WordPress plugin before 4.0.1, allows authenticated users with a role as low as contributor, to access arbitrary post metadata. This could lead to sensitive data disclosure, for example when used in combination with WooCommerce, the email address of orders can be retrieved","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.1 - Unauthorised Arbitrary Post Metadata Access","id":"CVE-2021-24824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Custom Content Shortcode \u003c 4.0.2 - Authenticated Arbitrary File Access / LFI","id":"CVE-2021-24825"},"packages":[],"prev":{"headline":"Support Board \u003c 3.3.6 - Arbitrary File Deletion via CSRF","id":"CVE-2021-24823"},"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":5.4,"headline":"Custom Content Shortcode \u003c 4.0.2 - Authenticated Stored Cross-Site Scripting","id":"CVE-2021-24826","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 contributors can access arbitrary post metadata, potentially exposing sensitive data like customer emails in WooCommerce.","url":"https://insights.sbomify.com/CVE-2021-24824/"}