{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1153 exists.","fix":"No fix has been published for CVE-2026-1153 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1153 is a medium-severity vulnerability in technical-laohu mpay, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-1153 and fix it if it is affected.\n\nWhat it is: CVE-2026-1153 is a medium-severity vulnerability in technical-laohu mpay, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1153 exists.\n\nAffected product: technical-laohu mpay. 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-1153/ (Markdown: https://insights.sbomify.com/CVE-2026-1153/index.md)","id":"CVE-2026-1153","markdown":"https://insights.sbomify.com/CVE-2026-1153/index.md","name":"CVE-2026-1153","record":{"aliases":["GHSA-jg8v-v78g-vjrq"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"mpay web application","requires_auth":"none","summary":"Remote attackers can perform cross-site request forgery attacks against the mpay web application, potentially bypassing security controls.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"mpay","vendor":"technical-laohu"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A vulnerability was detected in technical-laohu mpay up to 1.2.4. This affects an unknown function. Performing a manipulation results in cross-site request forgery. Remote exploitation of the attack is possible. The exploit is now public and may be used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"technical-laohu mpay cross-site request forgery","id":"CVE-2026-1153","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"SourceCodester E-Learning System Lesson index.php cross site scripting","id":"CVE-2026-1154"},"packages":[],"prev":{"headline":"technical-laohu mpay QR Code Image unrestricted upload","id":"CVE-2026-1152"},"products":["mpay"],"published":"2026-01-19","related":[{"cvss_score":5.1,"headline":"technical-laohu mpay QR Code Image unrestricted upload","id":"CVE-2026-1152","kev_date_added":null,"published":"2026-01-19"},{"cvss_score":4.8,"headline":"technical-laohu mpay User Center cross site scripting","id":"CVE-2026-1151","kev_date_added":null,"published":"2026-01-19"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["technical-laohu"]},"summary":"Remote attackers can perform cross-site request forgery attacks against the mpay web application, potentially bypassing security controls.","url":"https://insights.sbomify.com/CVE-2026-1153/"}