{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-3638 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-3638 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-3638 is a high-severity code injection vulnerability in n/a, published on 21 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-3638 and fix it if it is affected.\n\nWhat it is: CVE-2015-3638 is a high-severity code injection vulnerability in n/a, published on 21 Jul 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-2015-3638 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-2015-3638/ (Markdown: https://insights.sbomify.com/CVE-2015-3638/index.md)","id":"CVE-2015-3638","markdown":"https://insights.sbomify.com/CVE-2015-3638/index.md","name":"CVE-2015-3638","record":{"aliases":["GHSA-fx89-qj4v-348g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP backup tool","requires_auth":"low_privilege","summary":"Authenticated attackers can execute arbitrary PHP code in phpMyBackupPro by injecting scripts via specific parameters or configuration variables.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phpmybackuppro","vendor":"phpmybackuppro"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"phpMyBackupPro before 2.5 does not validate integer input, which allows remote authenticated users to execute arbitrary PHP code by injecting scripts via the path, filename, and period parameters to scheduled.php, and making requests to injected scripts, or by injecting PHP into a PHP configuration variable via a PHP variable variable.","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":"Code injection in n/a","id":"CVE-2015-3638","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2015"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2015-3639"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2015-3637"},"products":["n/a"],"published":"2017-07-21","related":[{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2015-3639","kev_date_added":null,"published":"2017-07-21"},{"cvss_score":8.1,"headline":"SQL injection in n/a","id":"CVE-2015-3637","kev_date_added":null,"published":"2017-12-27"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2015-4180","kev_date_added":null,"published":"2017-08-25"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2015-4181","kev_date_added":null,"published":"2017-08-25"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2015-3640","kev_date_added":null,"published":"2017-07-21"},{"cvss_score":7.1,"headline":"Cross-Site Scripting (XSS) vulnerability on PhpMyBackupPro","id":"CVE-2024-5413","kev_date_added":null,"published":"2024-05-28"}],"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)"}],"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 in phpMyBackupPro by injecting scripts via specific parameters or configuration variables.","url":"https://insights.sbomify.com/CVE-2015-3638/"}