{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25363 exists.","fix":"No fix has been published for CVE-2018-25363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-25363 is a medium-severity vulnerability in Fyffe PHP-Twitter-Clone, published on 25 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-25363 and fix it if it is affected.\n\nWhat it is: CVE-2018-25363 is a medium-severity vulnerability in Fyffe PHP-Twitter-Clone, published on 25 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25363 exists.\n\nAffected product: Fyffe PHP-Twitter-Clone. 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-2018-25363/ (Markdown: https://insights.sbomify.com/CVE-2018-25363/index.md)","id":"CVE-2018-25363","markdown":"https://insights.sbomify.com/CVE-2018-25363/index.md","name":"CVE-2018-25363","record":{"aliases":["GHSA-4gj8-55p5-fm24"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP Twitter Clone","requires_auth":"low_privilege","summary":"Attackers can force authenticated users to delete arbitrary posts via crafted malicious HTML forms targeting the tweet deletion endpoint.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Twitter-Clone 1 contains a cross-site request forgery vulnerability that allows remote attackers to force victims to delete posts by crafting malicious HTML forms. Attackers can create hidden forms targeting tweetdel.php with tweet IDs and automatically submit them to delete arbitrary posts from authenticated user sessions.","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":"Twitter-Clone 1 Cross-Site Request Forgery via tweetdel.php","id":"CVE-2018-25363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Twitter-Clone 1 SQL Injection via search.php","id":"CVE-2018-25364"},"packages":[],"prev":{"headline":"Twitter-Clone 1 SQL Injection via follow.php","id":"CVE-2018-25362"},"products":["PHP-Twitter-Clone"],"published":"2026-05-25","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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-26","vendors":["Fyffe"]},"summary":"Attackers can force authenticated users to delete arbitrary posts via crafted malicious HTML forms targeting the tweet deletion endpoint.","url":"https://insights.sbomify.com/CVE-2018-25363/"}