CVE-2026-77143

Broken Access Control in extension "Forum" (pforum)

Published Aug 25, 2026 CVSS 4.0 · 8.8 High EPSS < 1% KEV · Not listed
Description
The frontend topic editing flow does not verify on the server side that the requesting visitor owns the topic being modified. As a result, a visitor who knows the identifier of a topic from the public forum can submit a modified update request for that topic directly and overwrite its content, without the application confirming ownership. Topic identifiers are visible in the public forum listing, and exploitation requires no privileged access or non-default configuration.

Analysis

AI-generated

Technical impact

The Forum extension fails to verify that a visitor owns the topic they wish to edit; a user can supply the topic identifier in a request and replace the original content. This flaw allows an unauthenticated visitor to rewrite any topic in the public forum. The lack of server‑side ownership checks means the application accepts the update without confirming the submitter’s authority, resulting in a direct integrity compromise.

Affected Systems

TYPO3 Extension "Forum" (pforum). The vulnerability applies to any deployment of the extension where topic identifiers are publicly exposed and the editing endpoint is reachable. No specific version information is provided; the issue exists as long as the current codebase remains unchanged.

Risk and Exploitability

With a CVSS score of 8.8, the exploit has high impact. The attacker need only know a topic’s identifier, which is visible in the forum listing, and does not require privileged access or special configuration. The attack vector is an HTTP request to the editing endpoint; it relies on server‑side logic that omits ownership validation. Because no exploitation steps are constrained by authentication, any public user can alter content, and the EPSS score is not available. The vulnerability is not listed in CISA’s KEV catalog.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update or upgrade the Forum extension to the latest version that includes a fix for the ownership check omission.
  • If an update is unavailable, restrict the edit endpoint to authenticated users only, ensuring that only the topic owner can submit changes. Use TYPO3’s core access control settings or custom middleware to enforce ownership verification.
  • Until a patch or whitelist is applied, consider disabling the forum feature or removing the extension from production sites to prevent exploitation.

Generated by OpenCVE AI on August 25, 2026 at 10:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Typo3
Typo3 extension "forum"
Vendors & Products Typo3
Typo3 extension "forum"
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The frontend topic editing flow does not verify on the server side that the requesting visitor owns the topic being modified. As a result, a visitor who knows the identifier of a topic from the public forum can submit a modified update request for that topic directly and overwrite its content, without the application confirming ownership. Topic identifiers are visible in the public forum listing, and exploitation requires no privileged access or non-default configuration.
Title Broken Access Control in extension "Forum" (pforum)
Weaknesses CWE-639
CWE-862
References
Metrics cvssV4_0

{'score': 8.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
TYPO3
Published
Updated
Aug 26, 2026, 6:02 AM
Reserved
Aug 20, 2026, 1:10 PM
Status
Deferred
Published
Aug 25, 2026, 9:17 AM
Modified
Sep 28, 2026, 11:10 PM