{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25261 exists.","fix":"No fix has been published for CVE-2023-25261 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25261 is a critical code injection vulnerability in n/a, published on 27 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-25261 and fix it if it is affected.\n\nWhat it is: CVE-2023-25261 is a critical code injection vulnerability in n/a, published on 27 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25261 exists.\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-2023-25261/ (Markdown: https://insights.sbomify.com/CVE-2023-25261/index.md)","id":"CVE-2023-25261","markdown":"https://insights.sbomify.com/CVE-2023-25261/index.md","name":"CVE-2023-25261","record":{"aliases":["GHSA-fj34-r2c9-hq4p"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Stimulsoft reporting tools","requires_auth":"none","summary":"Attackers can inject source code into Stimulsoft reports to execute arbitrary commands and access local files.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"designer","vendor":"stimulsoft"},{"product":"viewer","vendor":"stimulsoft"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Certain Stimulsoft GmbH products are affected by: Remote Code Execution. This affects Stimulsoft Designer (Desktop) 2023.1.4 and Stimulsoft Designer (Web) 2023.1.3 and Stimulsoft Viewer (Web) 2023.1.3. Access to the local file system is not prohibited in any way. Therefore, an attacker may include source code which reads or writes local directories and files. It is also possible for the attacker to prepare a report which has a variable that holds the gathered data and render it in the report.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-03-02","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-03-02T07:53:41Z","kind":"github_poc","ref":"https://github.com/trustcves/CVE-2023-25261","stars":0,"title":null}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2023-25261","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2023-25262"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2023-25260"},"products":["n/a"],"published":"2023-03-27","related":[{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2023-25260","kev_date_added":null,"published":"2023-03-28"},{"cvss_score":7.5,"headline":"Server-side request forgery in n/a","id":"CVE-2023-25262","kev_date_added":null,"published":"2023-03-28"},{"cvss_score":5.5,"headline":"Weak cryptography in n/a","id":"CVE-2023-25263","kev_date_added":null,"published":"2023-03-27"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"Attackers can inject source code into Stimulsoft reports to execute arbitrary commands and access local files.","url":"https://insights.sbomify.com/CVE-2023-25261/"}