Skip to content
Noroxi
CVE-2026-47351· NVD / CVE Program· CNA TYPO3

TYPO3 CMS - Broken Access Control in Clipboard

Noroxi assessment

Priority: Monitor (action score 21/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.41% (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 TYPO3 CMS 13.4.31, 14.3.3.

Low priority for now. Upgrade to TYPO3 TYPO3 CMS 13.4.31, 14.3.3 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

Backend users were able to insert arbitrary records and files into the TYPO3 clipboard without proper read permission checks, which allowed users to gather information about records and files they were not authorized to view. This issue affects TYPO3 CMS versions 10.4.0-13.4.30 and 14.0.0-14.3.2.

MediumCVSS 5.3 · v4.0—No exploit Fix available
Published
Jun 9, 2026
Updated
Jul 23, 2026
EPSS
0.4% · 34th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · TYPO3
5.3
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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.

Follow CVE-2026-47351

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

—

Versions reported by the vendor

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

  • TYPO3 TYPO3 CMS

    • 10.4.0 and later · before 13.4.31affected · semver
    • 14.0.0 and later · before 14.3.3affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Packagisttypo3/cms-backendfrom 11.0.0 · before 11.5.5111.5.51
Packagisttypo3/cms-backendfrom 12.0.0 · before 12.4.4612.4.46
Packagisttypo3/cms-backendfrom 13.0.0 · before 13.4.3113.4.31
Packagisttypo3/cms-backendfrom 14.0.0 · before 14.3.314.3.3
Packagisttypo3/cms-backendbefore 10.4.5710.4.57
Packagisttypo3/cms-corefrom 11.0.0 · before 11.5.5111.5.51
Packagisttypo3/cms-corefrom 12.0.0 · before 12.4.4612.4.46
Packagisttypo3/cms-corefrom 13.0.0 · before 13.4.3113.4.31
Packagisttypo3/cms-corefrom 14.0.0 · before 14.3.314.3.3
Packagisttypo3/cms-corebefore 10.4.5710.4.57

Other highest-scoring records for the same primary product.

  • CVE-2026-49741TYPO3 CMS - Privilege Escalation & SQL Injection in Form Framework
    34Monitor
  • CVE-2026-85400TYPO3 CMS - Missing Authorization in lowlevel commands
    30Monitor
  • CVE-2026-47346TYPO3 CMS - Broken Access Control in Form Framework
    30Monitor
  • CVE-2026-11607TYPO3 CMS - Broken Access Control in Form Framework
    30Monitor
  • CVE-2026-19418TYPO3 CMS - Broken Access Control in Backend and Install Tool
    29Monitor
  • CVE-2026-49742TYPO3 CMS - Broken Access Control in Media Module
    28Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
TYPO3 TYPO3 CMS13.4.31Vendor (CNA)
TYPO3 TYPO3 CMS14.3.3Vendor (CNA)
Packagist:typo3/cms-backend10.4.57Package registry (OSV)
Packagist:typo3/cms-backend11.5.51Package registry (OSV)
Packagist:typo3/cms-backend12.4.46Package registry (OSV)
Packagist:typo3/cms-backend13.4.31Package registry (OSV)
Packagist:typo3/cms-backend14.3.3Package registry (OSV)
Packagist:typo3/cms-core10.4.57Package registry (OSV)
Packagist:typo3/cms-core11.5.51Package registry (OSV)
Packagist:typo3/cms-core12.4.46Package registry (OSV)
Packagist:typo3/cms-core13.4.31Package registry (OSV)
Packagist:typo3/cms-core14.3.3Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

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

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

Variant candidates

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

  • CVE-2026-7713291 days apartTYPO3 CMS - Information Disclosure via Backend Localization Wizard
    21Monitor

Chain candidates

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

—

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
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

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

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

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

References

All records