dbcve.org
Ultimate Bulletin BoardApplication · Infopop

CVE-2022-25091

MEDIUM · 5.3 CVSS v3.1 Published 2023-04-27
Fix available
A fix is available. Upgrade to after 5.47a or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Infopop Ultimate Bulletin Board up to v5.47a was discovered to allow all messages posted inside private forums to be disclosed by unauthenticated users via the quote reply feature.

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

Infopop Ultimate Bulletin Board (UBB) up to v5.47a contains an insecure direct object reference or broken access control vulnerability in the quote reply feature. Unauthenticated users can exploit this feature to read messages posted within private forums that should only be accessible to authenticated, authorized members.

MitigationUpgrade to a patched version if available. If no patch exists, disable or restrict the quote reply feature for unauthenticated access, or implement web application firewall rules to block unauthorized access to private forum content.

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
Ultimate Bulletin BoardApplication
Affected:<= 5.47a

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Identify UBB installation and version
    Locate the UBB installation and check the version number displayed in the admin panel, footer, or version file. Compare your installed version to the affected range (<= 5.47a).
    Affected if The installed version is 5.47a or earlier
  2. Verify if quote reply feature allows unauthenticated access
    Attempt to access the quote reply functionality on the forum without logging in. Look for the quote reply URL or button that allows quoting posts in replies.
    Affected if The quote reply feature is accessible and functional without authentication
  3. Test private forum access via quote feature
    Use the unauthenticated quote reply mechanism to access messages posted in forums marked as private or restricted to members only. Observe if private content is displayed.
    Affected if Private forum content is visible or accessible through the quote reply feature without being logged in
  4. Check for IDOR vulnerability in message references
    Examine the quote reply requests for direct object references such as message IDs or thread IDs in the URL or form parameters. Try modifying these identifiers to access other messages.
    Affected if Message or thread IDs can be manipulated to retrieve content from private forums without authentication

A user is affected if they are running UBB version 5.47a or earlier AND the quote reply feature is accessible to unauthenticated users, allowing them to read private forum content.

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
Upgrade available Upgrade to a release after 5.47a
Interim mitigation

Upgrade to a patched version if available. If no patch exists, disable or restrict the quote reply feature for unauthenticated access, or implement web application firewall rules to block unauthorized access to private forum content.

Recommended fix Moderate confidence

UBB Classic version 5.47b or later (latest 5.x release from ubbdev.com)

  1. Identify the current UBB Classic installation version by accessing the admin control panel or checking version.php
  2. If running version 5.47a or below, obtain the latest available UBB Classic release from the official vendor (currently at ubbdev.com)
  3. Backup the entire forum database and file system before performing any upgrade
  4. Upload all new files from the upgrade package, preserving custom templates and configuration
  5. Run any provided database upgrade scripts included in the new version
  6. Verify the quote reply feature now correctly enforces authentication for private forums
  7. Test that unauthenticated users receive an access denied message when attempting to access private forum content via any method
Caveat Custom templates and third-party hacks may require testing or modification after upgrade; ensure theme compatibility with new version

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

Fix this in Ultimate Bulletin Board Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25091 — 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-2022-25091 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