CVE-2005-4481: n/a vulnerability

CVE-2005-4481: Cross-site scripting (XSS) vulnerability in Polopoly 9 and earlier allows remote attackers to inject arbitr...

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

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 23:46 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2005-4481 describes a reported XSS issue in Polopoly 9 and earlier search functionality. The key business point is uncertainty: CVE notes the vendor disputed it as a custom-site implementation issue, not a product flaw. Treat this as an exposure-confirmation item for legacy Polopoly deployments, not a confirmed actively exploited emergency. Exposure is most plausible for internet-facing sites running Polopoly 9 or earlier with custom search handling. Because the affected product data is listed as n/a and the vendor disputed product impact, vulnerability managers must validate each implementation before assigning exposure. Handle as a targeted legacy-web assessment. It is not supported as a confirmed active exploitation event, but public-facing legacy search pages can create session and content-integrity risk if XSS is present. Mitigation focus: Inventory any Polopoly 9 or earlier deployments and public search pages.; Check vendor or maintainer guidance before assuming a product patch exists.; Review custom search implementations for safe parameter handling and output encoding..

Prepared: Jun 29, 2026, 15:35 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-4481 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 22, 2005, 11:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.