{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47916 exists.","fix":"No fix has been published for CVE-2025-47916 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-47916 is a critical code injection vulnerability in invisioncommunity Invision Power Board, published on 16 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47916 and fix it if it is affected.\n\nWhat it is: CVE-2025-47916 is a critical code injection vulnerability in invisioncommunity Invision Power Board, published on 16 May 2025. 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-2025-47916 exists.\n\nAffected product: invisioncommunity Invision Power Board. 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-2025-47916/ (Markdown: https://insights.sbomify.com/CVE-2025-47916/index.md)","id":"CVE-2025-47916","markdown":"https://insights.sbomify.com/CVE-2025-47916/index.md","name":"CVE-2025-47916","record":{"aliases":["GHSA-96q3-fjrx-h9hh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Invision Community","requires_auth":"none","summary":"Unauthenticated attackers can execute arbitrary PHP code by injecting crafted template strings into the theme editor.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"invisioncommunity","vendor":"invisioncommunity"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-1336","name":"Improper Neutralization of Special Elements Used in a Template Engine"}],"description":"Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2025-05-16","github_poc":1,"max_poc_stars":1,"metasploit":1,"nuclei":1,"refs":[{"date":"2025-11-21T13:16:49Z","kind":"github_poc","ref":"https://github.com/Web3-Serializer/CVE-2025-47916","stars":1,"title":"Proof‑of‑concept description for CVE‑2025‑47916, a Remote Code Execution vulnerability affecting Invision Community 5.0.0–5.0.6 via unsafe template processing in the \"customCss()\" method."},{"date":"2025-05-16","kind":"metasploit","ref":"exploit/multi/http/invision_customcss_rce","stars":null,"title":"Invision Community 5.0.6 customCss RCE"},{"date":"2025-05-18","kind":"exploitdb","ref":"52294","stars":null,"title":"Invision Community 5.0.6 - Remote Code Execution (RCE)"},{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-47916.yaml","stars":null,"title":"Invision Community \u003c=5.0.6 Unauthenticated RCE via Template Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in Invision Power Board","id":"CVE-2025-47916","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in mbedtls","id":"CVE-2025-47917"},"packages":[],"prev":{"headline":"reserved but not needed","id":"CVE-2025-47915"},"products":["Invision Power Board"],"published":"2025-05-16","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-30163","kev_date_added":null,"published":"2024-06-07"}],"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":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-17","vendors":["invisioncommunity"]},"summary":"Unauthenticated attackers can execute arbitrary PHP code by injecting crafted template strings into the theme editor.","url":"https://insights.sbomify.com/CVE-2025-47916/"}