dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-48613

MEDIUM · 5.9 CVSS v3.0 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
SQL injection vulnerability in phpBB profile field migration due to improper handling of user-supplied profile field data during migration, allowing execution of arbitrary SQL queries. Only applies to phpBB forums that had been updated from versions prior to phpBB 3.3.8 and have not been updated to 3.3.11 or newer yet.

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 · moderate confidence

SQL injection vulnerability in phpBB's profile field migration feature. The migration process improperly sanitizes user-supplied profile field data, enabling attackers to inject and execute arbitrary SQL queries. This only affects forums that originated on phpBB versions prior to 3.3.8 and remain on versions below 3.3.11.

MitigationUpdate phpBB to version 3.3.11 or newer to patch the vulnerable migration code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed phpBB version
    Access the Admin Control Panel > General tab > Server configuration > Server load, or look for a version file in your phpBB root directory (often includes version info in docs/ or in the admin dashboard).
    Affected if Installed version is below 3.3.11 (e.g., 3.3.10, 3.3.9, 3.3.8, 3.3.7, etc.)
  2. Determine original installation version
    Review your phpBB upgrade history or check the database for version records. Look in the phpbb_config table for keys like 'version' or check any upgrade logs from previous migrations. The key information is whether the forum was first installed on a version prior to 3.3.8.
    Affected if The forum was originally installed or ran on phpBB versions before 3.3.8 (any 3.2.x or early 3.3.x versions)
  3. Identify profile field migration feature
    In the Admin Control Panel, navigate to the profile fields section or look for migration-related tools. The vulnerable component is the profile field migration process that handles converting profile fields during version upgrades.
    Affected if Profile field migration feature exists and was run during an upgrade from an older phpBB version
  4. Confirm vulnerability window is applicable
    Verify that the forum was upgraded from a pre-3.3.8 version AND currently runs below 3.3.11. Both conditions must be true.
    Affected if Forum originated on < 3.3.8 AND current version is < 3.3.11

A user is affected if their phpBB forum was originally installed on a version prior to 3.3.8 and is currently running any version below 3.3.11, with the profile field migration feature having been used during an upgrade.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update phpBB to version 3.3.11 or newer to patch the vulnerable migration code.

Recommended fix High confidence

phpBB 3.3.11 or newer (latest 3.3.x release)

  1. Confirm current phpBB version is below 3.3.11
  2. Back up the phpBB database and all files
  3. Download phpBB 3.3.11 or the latest stable 3.3.x release from the official phpBB website
  4. Upload the new files, overwriting existing files while preserving the config.php file
  5. Run the database update script by accessing /install/app.php (or /install/index.php depending on version)
  6. Complete the upgrade process and verify the board is functional
  7. Ensure custom profile fields are functioning correctly after migration
Caveat Minor phpBB version updates typically do not introduce breaking changes, but always backup before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48613 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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