{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24680 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24680 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24680 is a medium-severity cross-site scripting vulnerability in Unknown WP Travel Engine – Travel and Tour Booking Plugin, published on 3 Jan 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-24680 and fix it if it is affected.\n\nWhat it is: CVE-2021-24680 is a medium-severity cross-site scripting vulnerability in Unknown WP Travel Engine – Travel and Tour Booking Plugin, published on 3 Jan 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-24680 in the wild and no public exploit code.\n\nAffected product: Unknown WP Travel Engine – Travel and Tour Booking Plugin. 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-24680/ (Markdown: https://insights.sbomify.com/CVE-2021-24680/index.md)","id":"CVE-2021-24680","markdown":"https://insights.sbomify.com/CVE-2021-24680/index.md","name":"CVE-2021-24680","record":{"aliases":["GHSA-3v2q-4w56-hr98"],"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":"Editors can inject malicious scripts via unescaped fields in WP Travel Engine, potentially compromising admin sessions and site integrity.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_travel_engine","vendor":"wptravelengine"}],"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 WP Travel Engine WordPress plugin before 5.3.1 does not escape the Description field in the Trip Destination/Activities/Trip Type and Pricing Category pages, allowing users with a role as low as editor to perform Stored Cross-Site Scripting attacks, even when the unfiltered_html capability 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":"WP Travel Engine \u003c 5.3.1 - Editor+ Stored Cross-Site Scripting","id":"CVE-2021-24680","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Duplicate Page \u003c= 4.4.2 - Admin+ Stored Cross-Site Scripting","id":"CVE-2021-24681"},"packages":[],"prev":{"headline":"Bitcoin / AltCoin Payment Gateway for WooCommerce \u003c 1.6.1 - Reflected Cross-Site Scripting","id":"CVE-2021-24679"},"products":["WP Travel Engine – Travel and Tour Booking Plugin"],"published":"2022-01-03","related":[{"cvss_score":9.3,"headline":"WordPress WP Travel Engine plugin \u003c= 5.7.9 - Unauth. Blind SQL Injection vulnerability","id":"CVE-2024-30502","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":8.1,"headline":"WordPress WP Travel Engine plugin \u003c= 6.3.5 - Local File Inclusion vulnerability","id":"CVE-2025-30870","kev_date_added":null,"published":"2025-04-01"},{"cvss_score":7.6,"headline":"WordPress WP Travel Engine plugin \u003c= 5.7.9 - SQL Injection vulnerability","id":"CVE-2024-30504","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":7.5,"headline":"WP Travel Engine \u003c= 6.5.1 - Missing Authorization to Unauthenticated Arbitrary Post Deletion","id":"CVE-2025-5282","kev_date_added":null,"published":"2025-06-13"},{"cvss_score":7.5,"headline":"WordPress WP Travel Engine plugin \u003c= 6.3.5 - Local File Inclusion vulnerability","id":"CVE-2025-30871","kev_date_added":null,"published":"2025-03-27"},{"cvss_score":7.5,"headline":"WordPress WP Travel Engine plugin \u003c= 5.8.0 - Price Manipulation vulnerability","id":"CVE-2024-32798","kev_date_added":null,"published":"2024-06-09"},{"cvss_score":6.5,"headline":"Cross-site scripting in WP Travel Engine","id":"CVE-2024-37944","kev_date_added":null,"published":"2024-07-20"}],"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":"Editors can inject malicious scripts via unescaped fields in WP Travel Engine, potentially compromising admin sessions and site integrity.","url":"https://insights.sbomify.com/CVE-2021-24680/"}