{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-6382 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6382 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6382 is a medium-severity cross-site scripting vulnerability in Taeggie Feed, published on 24 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6382 and fix it if it is affected.\n\nWhat it is: CVE-2025-6382 is a medium-severity cross-site scripting vulnerability in Taeggie Feed, published on 24 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6382 in the wild and no public exploit code.\n\nAffected product: Taeggie Feed. 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-2025-6382/ (Markdown: https://insights.sbomify.com/CVE-2025-6382/index.md)","id":"CVE-2025-6382","markdown":"https://insights.sbomify.com/CVE-2025-6382/index.md","name":"CVE-2025-6382","record":{"aliases":["GHSA-rv4p-hv2v-9w74"],"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 attackers can inject arbitrary scripts via the name attribute in the Taeggie Feed plugin, leading to stored XSS execution.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"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 Taeggie Feed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's taeggie-feed shortcode in all versions up to, and including, 0.1.10. The plugin’s render() method takes the user-supplied name attribute and injects it directly into a \u003cscript\u003e tag - both in the id attribute and inside jQuery.getScript() - without proper escaping. This makes it possible for authenticated attackers, with contributor-level access and above, 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":"Taeggie Feed \u003c= 0.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting via name Attribute","id":"CVE-2025-6382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"WP-PhotoNav \u003c= 1.2.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via photonav Shortcode","id":"CVE-2025-6383"},"packages":[],"prev":{"headline":"BeeTeam368 Extensions \u003c= 2.3.4 - Authenticated (Subscriber+) Directory Traversal to Arbitrary File Deletion","id":"CVE-2025-6381"},"products":["Taeggie Feed"],"published":"2025-07-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["taeggie"]},"summary":"Authenticated attackers can inject arbitrary scripts via the name attribute in the Taeggie Feed plugin, leading to stored XSS execution.","url":"https://insights.sbomify.com/CVE-2025-6382/"}