{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-8677 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-8677 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-8677 is a medium-severity code injection vulnerability in n/a, published on 31 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-8677 and fix it if it is affected.\n\nWhat it is: CVE-2014-8677 is a medium-severity code injection vulnerability in n/a, published on 31 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2014-8677 in the wild and no public exploit code.\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-2014-8677/ (Markdown: https://insights.sbomify.com/CVE-2014-8677/index.md)","id":"CVE-2014-8677","markdown":"https://insights.sbomify.com/CVE-2014-8677/index.md","name":"CVE-2014-8677","record":{"aliases":["GHSA-r3rc-xgjr-hc9q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"SOPlanning scheduling app","requires_auth":"low_privilege","summary":"Authenticated attackers can execute arbitrary PHP code via crafted database names in SOPlanning under specific configuration conditions.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"soplanning","vendor":"soplanning"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"The installation process for SOPlanning 1.32 and earlier allows remote authenticated users with a prepared database, and access to an existing database with a crafted name, or permissions to create arbitrary databases, or if PHP before 5.2 is being used, the configuration database is down, and smarty/templates_c is not writable to execute arbitrary php code via a crafted database name.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2015-07-13","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2015-07-13","kind":"exploitdb","ref":"37604","stars":null,"title":"SO Planning 1.32 - Multiple Vulnerabilities"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2014-8677","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2014"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2014-8678"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2014-8676"},"products":["n/a"],"published":"2017-08-31","related":[{"cvss_score":10,"headline":"Remote Code Execution through File Upload in SOPlanning before 1.52.02","id":"CVE-2024-27115","kev_date_added":null,"published":"2024-09-11"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-57169","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":9.8,"headline":"SQL Injection vulnerability in SOPlanning","id":"CVE-2024-9574","kev_date_added":null,"published":"2024-10-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-13963","kev_date_added":null,"published":"2021-03-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2014-8673","kev_date_added":null,"published":"2020-01-07"},{"cvss_score":9.3,"headline":"SQL Injection in SOPlanning before 1.52.02","id":"CVE-2024-27112","kev_date_added":null,"published":"2024-09-11"},{"cvss_score":9.3,"headline":"Insecure Direct Object Reference to export Database in SOPlanning before 1.52.02","id":"CVE-2024-27113","kev_date_added":null,"published":"2024-09-11"}],"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":"Authenticated attackers can execute arbitrary PHP code via crafted database names in SOPlanning under specific configuration conditions.","url":"https://insights.sbomify.com/CVE-2014-8677/"}