CVE-2005-4481

{"id": "CVE-2005-4481", "cveTags": [{"tags": ["disputed"], "sourceIdentifier": "cve@mitre.org"}], "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 6.8, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "MEDIUM", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.6, "obtainUserPrivilege": false, "obtainOtherPrivilege": true, "userInteractionRequired": false}]}, "published": "2005-12-22T11:03:00.000", "references": [{"url": "http://attrition.org/pipermail/vim/2006-September/001056.html", "source": "cve@mitre.org"}, {"url": "http://pridels0.blogspot.com/2005/12/polopoly-xss-vuln.html", "source": "cve@mitre.org"}, {"url": "http://www.osvdb.org/21878", "source": "cve@mitre.org"}, {"url": "http://www.securityfocus.com/bid/16007", "source": "cve@mitre.org"}, {"url": "http://attrition.org/pipermail/vim/2006-September/001056.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://pridels0.blogspot.com/2005/12/polopoly-xss-vuln.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.osvdb.org/21878", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.securityfocus.com/bid/16007", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-Other"}]}], "descriptions": [{"lang": "en", "value": "Cross-site scripting (XSS) vulnerability in Polopoly 9 and earlier allows remote attackers to inject arbitrary web script or HTML via unspecified search parameters. NOTE: the vendor has disputed this vulnerability, stating that the \"XSS flaw was only part of the custom implementation of the [polopoly] site\". As of 20061003, CVE has no further information on this issue, except that the original researcher has a history of testing live sites and assuming that discoveries indicate vulnerabilities in the associated package"}], "lastModified": "2024-11-21T00:04:21.727", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:polopoly:polopoly:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "DC6C08FF-3CB1-42BC-8ECE-ECA82E1F70AF", "versionEndIncluding": "9.0"}], "operator": "OR"}]}], "vendorComments": [{"comment": "1. The XSS flaw described was only part of the custom implementation of the http://www.polopoly.com/ site. It was never part of any version of any Polopoly product, nor delivered to any of Polopoly\u2019s customers.\n2. The XSS flaw that existed (the search form in the upper right corner) on the www.polopoly.com site has been fixed.\n3. When www.polopoly.com had the XSS flaw it was based on Polopoly 8.6. Polopoly 9.x was never involved what so ever in this issue. And as I said earlier, the flaw was not part of Polopoly 8.6 either, it was only in custom implementation code of the www.polopoly.com site.\n4. The www.polopoly.com site is not personalized nor permission controlled, so there was no information of any value to steal by exploiting the XSS flaw.", "lastModified": "2006-10-05T00:00:00", "organization": "Polopoly"}], "sourceIdentifier": "cve@mitre.org"}