{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-2129 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-2129 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-2129 is a medium-severity vulnerability in n/a, published on 1 May 2006."},"fix_prompt":"Check this codebase for CVE-2006-2129 and fix it if it is affected.\n\nWhat it is: CVE-2006-2129 is a medium-severity vulnerability in n/a, published on 1 May 2006. \nExploitation: There is no known exploitation of CVE-2006-2129 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-2006-2129/ (Markdown: https://insights.sbomify.com/CVE-2006-2129/index.md)","id":"CVE-2006-2129","markdown":"https://insights.sbomify.com/CVE-2006-2129/index.md","name":"CVE-2006-2129","record":{"aliases":["GHSA-m8qv-5p8w-9g69"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"pro_publish","vendor":"deltascripts"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:N","version":"2.0"},"cwes":[],"description":"Direct static code injection vulnerability in Pro Publish 2.0 allows remote authenticated administrators to execute arbitrary PHP code by editing certain settings, which are stored in set_inc.php.","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":"Direct static code injection vulnerability in Pro Publish 2.0 allows remote authenticated administrators to execute arbitrary PHP code by ed","id":"CVE-2006-2129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2006"},"n_packages":0,"n_references":6,"next":{"headline":"SQL injection in n/a","id":"CVE-2006-2130"},"packages":[],"prev":{"headline":"Multiple SQL injection vulnerabilities in Pro Publish 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) email and (2)","id":"CVE-2006-2128"},"products":["n/a"],"published":"2006-05-01","related":[{"cvss_score":7.5,"headline":"Multiple SQL injection vulnerabilities in Pro Publish 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) email and (2)","id":"CVE-2006-2128","kev_date_added":null,"published":"2006-05-01"},{"cvss_score":6.8,"headline":"Cross-site scripting in n/a","id":"CVE-2006-2821","kev_date_added":null,"published":"2006-06-05"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2006-2129/"}