{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-1273 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-1273 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-1273 is a critical vulnerability in n/a, published on 6 Apr 2010. It can be exploited over the network."},"fix_prompt":"Check this codebase for CVE-2010-1273 and fix it if it is affected.\n\nWhat it is: CVE-2010-1273 is a critical vulnerability in n/a, published on 6 Apr 2010. It can be exploited over the network.\nExploitation: There is no known exploitation of CVE-2010-1273 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2010-1273/ (Markdown: https://insights.sbomify.com/CVE-2010-1273/index.md)","id":"CVE-2010-1273","markdown":"https://insights.sbomify.com/CVE-2010-1273/index.md","name":"CVE-2010-1273","record":{"aliases":["GHSA-vfw6-frjc-c498"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Wt web toolkit","requires_auth":"unknown","summary":"Emweb Wt fails to validate UTF-8 encoding in form values and JSignal arguments, potentially allowing remote attackers to exploit unspecified impacts.","user_interaction":"unknown","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wt","vendor":"emweb"}],"cvss":{"score":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Emweb Wt before 3.1.1 does not validate the UTF-8 encoding of (1) form values and (2) JSignal arguments, which has unspecified impact and remote attack vectors.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2010-1273","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2010"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2010-1274"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2010-1272"},"products":["n/a"],"published":"2010-04-06","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Emweb Wt fails to validate UTF-8 encoding in form values and JSignal arguments, potentially allowing remote attackers to exploit unspecified impacts.","url":"https://insights.sbomify.com/CVE-2010-1273/"}