Is pear/http_request2 2.6 vulnerable?

Composer · 1 release from 2.6.0 to 2.6.0 · latest pear/http_request2 is 2.8.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. pear/http_request2 2.6.0, the last 2.6 release, is affected by 1 known security advisory (1 medium), including CVE-2025-43717. Upgrade to 2.7.0 or later to fix all of them.

Upgrade with:composer require pear/http_request2:^2.7.0

Is your project on an affected pear/http_request2?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting pear/http_request2 2.6.0

  • MediumCVE-2025-43717GHSA-w7gh-f2fm-9q8r17 Apr 2025

    PEAR HTTP_Request2 vulnerable to Cross-site Scripting

    Affected
    <2.7.0
    Fixed in
    2.7.0

Which of your client projects are still on pear/http_request2 2.6?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact pear/http_request2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other pear/http_request2 versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.