NVD / CVE Program· CNA GitHub_M

CVE-2022-23501: TYPO3 vulnerable to Improper Authentication in Frontend Login

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: typo3/cms (Packagist) 10.4.33, 11.5.20, 12.1.1; typo3/cms-core (Packagist) 10.4.33, 11.5.20, 12.1.1.

Low priority for now. Upgrade to typo3/cms (Packagist) 10.4.33, 11.5.20, 12.1.1; typo3/cms-core (Packagist) 10.4.33, 11.5.20, 12.1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

TYPO3 is an open source PHP based web content management system. In versions prior to 8.7.49, 9.5.38, 10.4.33, 11.5.20, and 12.1.1 TYPO3 is vulnerable to Improper Authentication. Restricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary. This issue is patched in versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1.

MediumCVSS 6.5 · v3.1—No exploit Fix available

Auth bypass

GHSA-jfp7-79g7-89rf

Published: Dec 14, 2022
Updated: Jun 17, 2026
EPSS: 0.5% · 43th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 6.5
CNA · GitHub_M: 5.9; 0.6 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
typo3	typo3	cpe:2.3:a:typo3:typo3

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

typo3 typo3before 8.7.49
typo3 typo39.0.0 and later · before 9.5.38
typo3 typo310.0.0 and later · before 10.4.33
typo3 typo311.0.0 and later · before 11.5.20
typo3 typo312.0.0 and later · before 12.1.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

TYPO3 typo3
- >= 8.0.0, < 8.7.49, >= 9.0.0, < 9.5.38, >= 10.0.0, < 10.4.33, >= 11.0.0, < 11.5.20, >= 12.0.0, < 12.1.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Packagist	typo3/cms	from 10.0.0 · before 10.4.33	10.4.33
Packagist	typo3/cms	from 11.0.0 · before 11.5.20	11.5.20
Packagist	typo3/cms	from 12.0.0 · before 12.1.1	12.1.1
Packagist	typo3/cms-core	from 10.0.0 · before 10.4.33	10.4.33
Packagist	typo3/cms-core	from 11.0.0 · before 11.5.20	11.5.20
Packagist	typo3/cms-core	from 12.0.0 · before 12.1.1	12.1.1
Packagist	typo3/cms-core	from 9.0.0 · before 9.5.38	9.5.38
Packagist	typo3/cms-core	before 8.7.49	8.7.49

Same product

typo3: all records

Other highest-scoring records for the same primary product.

CVE-2009-0255The System extension Install tool in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 creates the encryption key with
60This week
CVE-2013-6288Unspecified vulnerability in the Apache Solr for TYPO3 (solr) extension before 2.8.3 for TYPO3 has unknown impact and remote attack vectors,
41Plan
CVE-2013-5303Unspecified vulnerability in the Store Locator (locator) extension before 3.1.5 for TYPO3 has unknown impact and remote attack vectors, rela
41Plan

Published before and after this one in the same product

← EarlierCVE-2022-36108Sep 13, 2022 · Cross-Site Scripting in typo3/cms-core
24Monitor
← EarlierCVE-2022-23500Dec 14, 2022 · TYPO3 subject to Uncontrolled Recursion resulting in Denial of Service
30Monitor
Later →CVE-2022-23502Dec 14, 2022 · TYPO3 contains Insufficient Session Expiration after Password Reset
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Packagist:typo3/cms	10.4.33	Package registry (OSV)
Packagist:typo3/cms	11.5.20	Package registry (OSV)
Packagist:typo3/cms	12.1.1	Package registry (OSV)
Packagist:typo3/cms-core	10.4.33	Package registry (OSV)
Packagist:typo3/cms-core	11.5.20	Package registry (OSV)
Packagist:typo3/cms-core	12.1.1	Package registry (OSV)
Packagist:typo3/cms-core	8.7.49	Package registry (OSV)
Packagist:typo3/cms-core	9.5.38	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2022-235030 days apartTYPO3 vulnerable to Arbitrary Code Execution via Form Framework
35Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

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

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/TYPO3/typo3/security/advisories/GHSA-jfp7-79g7-89rf

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records