{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1494 exists.","fix":"No fix has been published for CVE-2015-1494 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-1494 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Feb 2015. 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-2015-1494 and fix it if it is affected.\n\nWhat it is: CVE-2015-1494 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Feb 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1494 exists.\n\nAffected product: n/a. 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-2015-1494/ (Markdown: https://insights.sbomify.com/CVE-2015-1494/index.md)","id":"CVE-2015-1494","markdown":"https://insights.sbomify.com/CVE-2015-1494/index.md","name":"CVE-2015-1494","record":{"aliases":["GHSA-44cc-c4hq-r7vv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Remote attackers can execute cross-site scripting attacks via the FancyBox plugin, requiring user interaction to trigger the malicious payload.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"fancybox","vendor":"colorlib"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The FancyBox for WordPress plugin before 3.0.3 for WordPress does not properly restrict access, which allows remote attackers to conduct cross-site scripting (XSS) attacks via an mfbfw[*] parameter in an update action to wp-admin/admin-post.php, as demonstrated by the mfbfw[padding] parameter and exploited in the wild in February 2015.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2015-02-16","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2015-02-16","kind":"exploitdb","ref":"36087","stars":null,"title":"WordPress Plugin Fancybox 3.0.2 - Persistent Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2015-1494","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2015"},"n_packages":0,"n_references":8,"next":{"headline":"Memory corruption in n/a","id":"CVE-2015-1495"},"packages":[],"prev":{"headline":"Moodle directory traversal vulnerability","id":"CVE-2015-1493"},"products":["n/a"],"published":"2015-02-17","related":[{"cvss_score":6.1,"headline":"FancyBox for WordPress \u003c 3.3.6 - Unauthenticated Stored XSS","id":"CVE-2025-3662","kev_date_added":null,"published":"2025-06-03"},{"cvss_score":4.4,"headline":"Cross-site scripting in FancyBox for WordPress","id":"CVE-2024-0662","kev_date_added":null,"published":"2024-04-09"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can execute cross-site scripting attacks via the FancyBox plugin, requiring user interaction to trigger the malicious payload.","url":"https://insights.sbomify.com/CVE-2015-1494/"}