{"answers":{"affected":"7 open source packages ship an affected version, including plone and Plone. It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-4194 in the wild and no public exploit code.","fix":"Upgrade plone to a fixed version for your release line: 4.1.1, 4.2.6 or 4.3.2.","what":"CVE-2013-4194 is a medium-severity vulnerability in Plone Plone, published on 11 Mar 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-2013-4194 and fix it if it is affected.\n\nWhat it is: CVE-2013-4194 is a medium-severity vulnerability in Plone Plone, published on 11 Mar 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-2013-4194 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- plone (PyPI): affected from 2.1; fixed in 4.1.1, 4.2.6, 4.3.2\n- plone (PyPI): affected from 2.1; fixed in 4.1.1\n- plone (PyPI): affected from 4.2; fixed in 4.2.6\n- plone (PyPI): affected from 4.3; fixed in 4.3.2\n- Plone (PyPI): affected from 2.1; fixed in 4.1.1\n- Plone (PyPI): affected from 4.2; fixed in 4.2.6\n- Plone (PyPI): affected from 4.3; fixed in 4.3.2\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-2013-4194/ (Markdown: https://insights.sbomify.com/CVE-2013-4194/index.md)","id":"CVE-2013-4194","markdown":"https://insights.sbomify.com/CVE-2013-4194/index.md","name":"CVE-2013-4194","record":{"aliases":["GHSA-mm32-jw73-9227","PYSEC-2014-58"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Plone CMS","requires_auth":"none","summary":"Remote attackers can obtain sensitive installation path information via crafted URLs in Plone's WYSIWYG component.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"plone","vendor":"plone"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The WYSIWYG component (wysiwyg.py) in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote attackers to obtain sensitive information via a crafted URL, which reveals the installation path in an error message.","ecosystems":["PyPI"],"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":"Plone is vulnerable to File System Path Exposure","id":"CVE-2013-4194","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"plone:plone","products":["plone:plone"],"type":"information_disclosure","year":"2013"},"n_packages":7,"n_references":4,"next":{"headline":"Plone Multiple open redirect vulnerabilities","id":"CVE-2013-4195"},"packages":[{"ecosystem":"PyPI","fixed":["4.1.1"],"introduced":["2.1"],"last_affected":[],"package":"Plone","purl":null,"source":"GHSA-mm32-jw73-9227"},{"ecosystem":"PyPI","fixed":["4.2.6"],"introduced":["4.2"],"last_affected":[],"package":"Plone","purl":null,"source":"GHSA-mm32-jw73-9227"},{"ecosystem":"PyPI","fixed":["4.3.2"],"introduced":["4.3"],"last_affected":[],"package":"Plone","purl":null,"source":"GHSA-mm32-jw73-9227"},{"ecosystem":"PyPI","fixed":["4.1.1","4.2.6","4.3.2"],"introduced":["2.1","4.2","4.3"],"last_affected":[],"package":"plone","purl":"pkg:pypi/plone","source":"PYSEC-2014-58"},{"ecosystem":"PyPI","fixed":["4.1.1"],"introduced":["2.1"],"last_affected":[],"package":"plone","purl":"pkg:pypi/plone","source":"GHSA-mm32-jw73-9227"},{"ecosystem":"PyPI","fixed":["4.2.6"],"introduced":["4.2"],"last_affected":[],"package":"plone","purl":"pkg:pypi/plone","source":"GHSA-mm32-jw73-9227"},{"ecosystem":"PyPI","fixed":["4.3.2"],"introduced":["4.3"],"last_affected":[],"package":"plone","purl":"pkg:pypi/plone","source":"GHSA-mm32-jw73-9227"}],"prev":{"headline":"Plone Unrestricted Filed Manipulation vulnerability via content edit forms","id":"CVE-2013-4193"},"products":["n/a"],"published":"2014-03-11","related":[{"cvss_score":9.9,"headline":"Incorrect Permission Assignment for Critical Resource in Plone","id":"CVE-2021-33509","kev_date_added":null,"published":"2021-05-21"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35190","kev_date_added":null,"published":"2020-12-17"},{"cvss_score":9.8,"headline":"Plone Unauthenticated Write Vulnerability","id":"CVE-2020-7941","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":9.3,"headline":"Zope Command Execution Vulnerability","id":"CVE-2011-3587","kev_date_added":null,"published":"2011-10-10"},{"cvss_score":8.8,"headline":"Server-Side Request Forgery in Plone CMS","id":"CVE-2021-33926","kev_date_added":null,"published":"2023-02-17"},{"cvss_score":8.8,"headline":"Improper Restriction of XML External Entity Reference in Plone","id":"CVE-2020-28734","kev_date_added":null,"published":"2020-12-30"},{"cvss_score":8.8,"headline":"SSRF attacks via tracebacks in Plone","id":"CVE-2020-28735","kev_date_added":null,"published":"2020-12-30"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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 obtain sensitive installation path information via crafted URLs in Plone's WYSIWYG component.","url":"https://insights.sbomify.com/CVE-2013-4194/"}