{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25753 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25753 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25753 is a critical vulnerability in Praskla-Technology assessment-placipy, published on 6 Feb 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-25753 and fix it if it is affected.\n\nWhat it is: CVE-2026-25753 is a critical vulnerability in Praskla-Technology assessment-placipy, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25753 in the wild and no public exploit code.\n\nAffected product: Praskla-Technology assessment-placipy. 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-25753/ (Markdown: https://insights.sbomify.com/CVE-2026-25753/index.md)","id":"CVE-2026-25753","markdown":"https://insights.sbomify.com/CVE-2026-25753/index.md","name":"CVE-2026-25753","record":{"aliases":["GHSA-6537-cf56-j9w2"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Placement management system","requires_auth":"none","summary":"PlaciPy uses a hard-coded default password for student accounts, allowing attackers to take over any student account.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"placipy","vendor":"prasklatechnology"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-259","name":"Use of Hard-coded Password"}],"description":"PlaciPy is a placement management system designed for educational institutions. In version 1.0.0, the application uses a hard-coded, static default password for all newly created student accounts. This results in mass account takeover, allowing any attacker to log in as any student once the password is known.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"PlaciPy has a Hard-Coded Default Password for All Student Accounts (Account Takeover)","id":"CVE-2026-25753","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"AdonisJS multipart body parsing has Prototype Pollution issue","id":"CVE-2026-25754"},"packages":[],"prev":{"headline":"FUXA Unauthenticated Remote Arbitrary Device Tag Write","id":"CVE-2026-25752"},"products":["assessment-placipy"],"published":"2026-02-06","related":[{"cvss_score":9.3,"headline":"PlaciPy is Missing CSRF Protection on State-Changing Endpoints","id":"CVE-2026-25812","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":9.3,"headline":"NoSQL Injection Risk via Unsanitized Query Parameters","id":"CVE-2026-25814","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":9.3,"headline":"PlaciPy Admin Privilege Escalation via Trusted JWT Claims","id":"CVE-2026-25875","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":8.7,"headline":"PlaciPy Exposes Sensitive Data via Application Logs","id":"CVE-2026-25813","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":5.3,"headline":"PlaciPy has Missing Authorization Checks on Student Management Endpoints (IDOR)","id":"CVE-2026-25806","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":5.3,"headline":"PlaciPy Code Execution Allowed Without Assessment Active State Validation","id":"CVE-2026-25809","kev_date_added":null,"published":"2026-02-09"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-09","vendors":["Praskla-Technology"]},"summary":"PlaciPy uses a hard-coded default password for student accounts, allowing attackers to take over any student account.","url":"https://insights.sbomify.com/CVE-2026-25753/"}