{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110025 exists.","fix":"No fix has been published for CVE-2026-110025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-110025 is a medium-severity vulnerability in slackero phpwcms, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-110025 and fix it if it is affected.\n\nWhat it is: CVE-2026-110025 is a medium-severity vulnerability in slackero phpwcms, published on 13 Oct 2026. 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-2026-110025 exists.\n\nAffected product: slackero phpwcms. 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-2026-110025/ (Markdown: https://insights.sbomify.com/CVE-2026-110025/index.md)","id":"CVE-2026-110025","markdown":"https://insights.sbomify.com/CVE-2026-110025/index.md","name":"CVE-2026-110025","record":{"aliases":["GHSA-2c7r-324f-fxm4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"phpwcms CMS","requires_auth":"none","summary":"Remote attackers can upload arbitrary files via the Extension Check component, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X","version":"4.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"A flaw has been found in slackero phpwcms up to 1.9.49/1.12.3. This issue affects some unknown processing of the file include/inc_front/content/cnt23.article.inc.php of the component Extension Check. This manipulation of the argument POST_name causes unrestricted upload. The attack can be initiated remotely. Upgrading to version 1.9.50 and 1.12.4 is capable of addressing this issue. Patch name: 118c978430f5a9668b30535f6e592c7ae8df711f/f4c136b467565b2d16ebe2b8276b9a03547a9a69/8571cb47df8d66804d1eb88ae3d1ab4fb513e1e7. Upgrading the affected component is recommended.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-13","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-13T22:45:00Z","kind":"github_poc","ref":"https://github.com/capivara-research/CVE-2026-110025","stars":0,"title":"CVE-2026-110025: bilingual analysis and safe local PoC for phpwcms unrestricted upload to RCE"}],"tier":"weaponised"},"has_fix":false,"headline":"slackero phpwcms Extension Check cnt23.article.inc.php unrestricted upload","id":"CVE-2026-110025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Tasty Recipes Lite 1.2 - 1.2.10 - Contributor+ Taxonomy Term Creation, Renaming and Deletion","id":"CVE-2026-110026"},"packages":[],"prev":{"headline":"@fastify/jwt vulnerable to missing token expiration when per-call options drop global defaults","id":"CVE-2026-110024"},"products":["phpwcms"],"published":"2026-10-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["slackero"]},"summary":"Remote attackers can upload arbitrary files via the Extension Check component, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-110025/"}