CVE-2001-1482
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL injection vulnerability in bb_memberlist.php for phpBB 1.4.2 allows remote attackers to execute arbitrary SQL queries via the $sortby variable.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in phpBB 1.4.2's bb_memberlist.php allows remote attackers to execute arbitrary SQL queries through the unsanitized $sortby parameter. This occurs because user-supplied input is directly incorporated into SQL queries without proper validation or parameterized queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.4.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm phpBB installation existsLocate phpBB by checking for common installation paths (e.g., /phpbb, /forum, /bbs) or search for characteristic phpBB files such as 'config.php' or 'viewforum.php' in the web root.Affected if phpBB is installed on the server
-
Identify installed phpBB versionExamine the phpBB version file or configuration. In phpBB 1.4.x, the version is typically defined in a file like 'includes/constants.php' or can be displayed in the admin control panel under 'System' or 'General Info'. Compare your installed version against the affected range.Affected if The installed version is exactly 1.4.2
-
Locate bb_memberlist.phpSearch the phpBB installation directory for the file 'bb_memberlist.php'. This file is typically found in the root phpBB directory.Affected if The file bb_memberlist.php exists in the phpBB installation
-
Verify memberlist functionality is accessibleConfirm that the memberlist feature is enabled and accessible. In phpBB 1.4.2, this feature is typically accessible via a 'memberlist' link on the forum, which triggers bb_memberlist.php. Check if unauthenticated or low-privilege users can access the memberlist.Affected if The memberlist feature is enabled and accessible to users who can trigger the vulnerable $sortby parameter
You are affected if phpBB version 1.4.2 is installed, bb_memberlist.php exists, and the memberlist functionality is accessible, allowing unsanitized input through the sortby parameter to reach the SQL query.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of phpBB or implement proper input validation and use parameterized queries for the $sortby parameter to prevent SQL injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-1482 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2001-1482 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data