{"answers":{"affected":"2 open source packages ship an affected version, including in2code/powermail. It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-6288 in the wild and no public exploit code.","fix":"Upgrade in2code/powermail to 2.0.11 or later.","what":"CVE-2014-6288 is a high-severity vulnerability in n/a, published on 3 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-6288 and fix it if it is affected.\n\nWhat it is: CVE-2014-6288 is a high-severity vulnerability in n/a, published on 3 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2014-6288 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- in2code/powermail (Packagist): affected from 2.0.0; fixed in 2.0.11\n- in2code/powermail (Packagist): affected from 2.0.0; fixed in 2.0.11\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-2014-6288/ (Markdown: https://insights.sbomify.com/CVE-2014-6288/index.md)","id":"CVE-2014-6288","markdown":"https://insights.sbomify.com/CVE-2014-6288/index.md","name":"CVE-2014-6288","record":{"aliases":["GHSA-2jq7-pgqq-gqqj"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 powermail extension","requires_auth":"none","summary":"Remote attackers can bypass CAPTCHA protection in the TYPO3 powermail extension, allowing automated spam or abuse.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"powermail","vendor":"alex_kellner"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"The powermail extension 2.x before 2.0.11 for TYPO3 allows remote attackers to bypass the CAPTCHA protection mechanism via unspecified vectors.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"TYPO3 powermail extension allows remote attackers to bypass CAPTCHA protection mechanism","id":"CVE-2014-6288","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2014"},"n_packages":2,"n_references":2,"next":{"headline":"yag and pt_extbase extensions for TYPO3 allow remote attackers to bypass access restrictions","id":"CVE-2014-6289"},"packages":[{"ecosystem":"Packagist","fixed":["2.0.11"],"introduced":["2.0.0"],"last_affected":[],"package":"in2code/powermail","purl":null,"source":"GHSA-2jq7-pgqq-gqqj"},{"ecosystem":"Packagist","fixed":["2.0.11"],"introduced":["2.0.0"],"last_affected":[],"package":"in2code/powermail","purl":"pkg:composer/in2code/powermail","source":"GHSA-2jq7-pgqq-gqqj"}],"prev":{"headline":"Rejetto HTTP File Server (HFS) Remote Code Execution","id":"CVE-2014-6287"},"products":["n/a"],"published":"2014-10-03","related":[{"cvss_score":7.5,"headline":"TYPO3 powermail extension has unrestricted file upload vulnerability","id":"CVE-2014-3947","kev_date_added":null,"published":"2014-10-03"},{"cvss_score":7.5,"headline":"powermail extension for TYPO3 vulnerable to SQL Injection","id":"CVE-2010-3604","kev_date_added":null,"published":"2010-09-24"},{"cvss_score":7.5,"headline":"TYPO3 powermail Extension Vulnerable to SQL Injection via Unspecified Vectors","id":"CVE-2010-0329","kev_date_added":null,"published":"2010-01-15"},{"cvss_score":5,"headline":"Business logic in n/a","id":"CVE-2010-3687","kev_date_added":null,"published":"2010-09-29"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2014-3948","kev_date_added":null,"published":"2014-06-04"},{"cvss_score":4.3,"headline":"powermail extension for TYPO3 has Cross-site Scripting vulnerability","id":"CVE-2012-5889","kev_date_added":null,"published":"2012-11-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-06","vendors":["n/a"]},"summary":"Remote attackers can bypass CAPTCHA protection in the TYPO3 powermail extension, allowing automated spam or abuse.","url":"https://insights.sbomify.com/CVE-2014-6288/"}