Skip to main content

FlatPress CVE-2026-56785

| EUVDEUVD-2026-38634 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-06-23 VulnCheck GHSA-gf5w-3f8w-9fm6
8.4
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify public FlatPress blog with comments enabled
  2. Delivery
    Submit comment with javascript: URI or HTML payload in name/url/email
  3. Exploit
    Payload stored unescaped in flat-file backend
  4. Execution
    Admin opens comment-list panel or visitor loads post
  5. Persist
    Script executes in victim browser context
  6. Impact
    Steal admin session or perform CMS actions

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The target FlatPress site must expose either the public comment form on a blog post or the contact form, both of which are enabled by default, and the attacker must be able to submit at least one comment/contact entry (no account required). Exploitation against an administrator additionally requires that the admin subsequently views the comment list in the admin panel or that another visitor loads the affected post page. Limiting factors: sites that have disabled commenting/contact, or that require pre-moderation by a user who never previews unmoderated content, materially reduce reachability; the bug is in the leggero theme template and admin comment list, so custom themes that already escape output may be unaffected.

Impact

The vendor CVSS 4.0 score of 8.4 (AV:N/AC:L/PR:N/UI:P/VC:H/VI:L/SC:H) reflects an unauthenticated, network-reachable stored XSS where the victim is most likely an authenticated administrator viewing the comment list - hence the high subsequent-system confidentiality impact (admin session/cookie theft, CMS takeover via the admin panel). User interaction is passive (UI:P) because simply viewing the affected page triggers the payload. EPSS and KEV signals were not provided in the input, and there is no public exploit identified at time of analysis, so this is not currently a mass-exploitation candidate; however, the disclosed patch diff effectively functions as an exploitation roadmap. Net real-world risk is moderate-to-high for any internet-exposed FlatPress instance accepting public comments, and lower for invitation-only or comment-disabled blogs.

Exploit ScenarioDerived

An unauthenticated attacker submits a comment on a public FlatPress blog post, placing a payload such as a javascript: URI in the URL field or an HTML/script fragment in the name field. When an administrator later opens the admin comment-list panel - or any reader views the post's comments - the payload executes in their browser context and can exfiltrate session cookies, perform CSRF-style actions against the admin panel, or pivot to full site takeover. A public proof-of-concept write-up exists at github.com/dilipk5/flatpressd-cms-sxss.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 23, 2026

Stored cross-site scripting in FlatPress (commits prior to 10be83c) allows unauthenticated remote attackers to inject persistent HTML and JavaScript via the name, URL, and email fields of comment and contact forms. The payloads execute in any viewer's browser - including administrators reviewing comments in the admin panel - and weak URL scheme validation additionally permits javascript: and data: URI injection. No public exploit identified at time of analysis, but the patch and a third-party advisory disclose the affected sinks in detail.

RemediationAI

Upstream fix available (commit 10be83c); released patched version not independently confirmed, so update FlatPress to a build that includes commit 10be83cbaac5ce0e51250b9d57de7f257b8f34f8 or later from https://github.com/flatpressblog/flatpress. As compensating controls until the upgrade is deployed, disable public commenting and the contact form in the FlatPress admin (eliminates the injection sinks but breaks reader engagement), require moderation of every comment before it appears (reduces window of exposure for admin viewers but does not protect the moderator themselves who views unmoderated comments), or apply the template change manually by adding the |wp_specialchars:1 Smarty modifier to $name, $url, and $email in admin/panels/entry/admin.entry.commentlist.tpl and fp-interface/themes/leggero/comments.tpl and backporting the parse_url-based scheme check in comments.php and contact.php. A site-wide Content-Security-Policy that forbids inline script and javascript:/data: URI navigation will blunt payload execution but may break legitimate themes or plugins that rely on inline handlers.

Affected VersionsENISA

FlatPress 0 ≤10be83c

Affected Packages

euvd flatpress no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

FlatPress is a flat-file PHP blog engine that renders user-submitted comment metadata through Smarty templates. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation): the templates admin/panels/entry/admin.entry.commentlist.tpl and fp-interface/themes/leggero/comments.tpl interpolated $name, $url, and $email directly into HTML without an output-encoding modifier, and the comments.php / contact.php sanitize_*() helpers only enforced an http(s):// prefix substring check rather than parsing the URL and validating the scheme via parse_url(). The fix adds the wp_specialchars:1 Smarty modifier at the sinks and rewrites the URL sanitizer to reject control characters, HTML-significant bytes, and any scheme other than http/https. CPE coverage (cpe:2.3:a:flatpress:flatpress:*) lists all versions as affected up to the fix commit.

Know when Flatpress gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.4 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
vuln.today AI 8.2 HIGH

Network-reachable stored XSS submittable without auth (PR:N), requires a victim to view the affected page (UI:R), and the script executes in the admin's authenticated context, changing scope (S:C) with high confidentiality impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
Low
Subsequent system: Availability
None

DescriptionCVE.org

FlatPress versions prior to commit 10be83c, contains a stored cross-site scripting vulnerability in comment and contact forms where name, URL, and email fields are rendered without proper output encoding in Smarty templates. Attackers can inject arbitrary HTML and JavaScript through these fields to execute malicious scripts in browsers of viewers including administrators, or bypass URL scheme validation to inject javascript: or data: URIs.

Executive ViewAI

Why It Matters

FlatPress contains a stored cross-site scripting (CVSS 8.4) vulnerability allowing unauthenticated attackers to inject malicious code through public comment and contact forms, with execution occurring when administrators review submissions in the backend. This creates direct risk of administrative account compromise, customer data theft, and website defacement. All FlatPress instances prior to commit 10be83c require immediate patching.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 85% exploitable
Prevalence
Low
niche open-source flat-file blog engine with small installed base
Social Media
2
Sightings
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2023-0947 CRITICAL POC
9.8 Feb 22

Path Traversal in GitHub repository flatpressblog/flatpress prior to 1.3. Rated critical severity (CVSS 9.8), this vulne

CVE-2022-4606 CRITICAL POC
9.8 Dec 18

PHP Remote File Inclusion in GitHub repository flatpressblog/flatpress prior to 1.3. Rated critical severity (CVSS 9.8),

CVE-2024-4023 HIGH POC
8.1 Mar 20

A stored cross-site scripting (XSS) vulnerability exists in flatpressblog/flatpress version 1.3. Rated high severity (CV

CVE-2023-1105 HIGH POC
8.1 Mar 01

External Control of File Name or Path in GitHub repository flatpressblog/flatpress prior to 1.3. Rated high severity (CV

CVE-2024-9847 HIGH POC
8.0 Mar 20

FlatPress CMS version latest is vulnerable to Cross-Site Request Forgery (CSRF) attacks that allow an attacker to enable

CVE-2022-40048 HIGH POC
7.2 Sep 29

Flatpress v1.2.1 was discovered to contain a remote code execution (RCE) vulnerability in the Upload File function. Rate

CVE-2025-29602 MEDIUM POC
6.1 May 07

flatpress 1.3.1 is vulnerable to Cross Site Scripting (XSS) in Administration area via Manage categories. Rated medium s

CVE-2024-25412 MEDIUM POC
6.1 Sep 27

A cross-site scripting (XSS) vulnerability in Flatpress v1.3 allows attackers to execute arbitrary web scripts or HTML v

CVE-2024-25411 MEDIUM POC
6.1 Sep 27

A cross-site scripting (XSS) vulnerability in Flatpress v1.3 allows attackers to execute arbitrary web scripts or HTML v

CVE-2023-1106 MEDIUM POC
6.1 Mar 02

Cross-site Scripting (XSS) - Reflected in GitHub repository flatpressblog/flatpress prior to 1.3. Rated medium severity

CVE-2022-4748 CRITICAL
9.8 Dec 27

A vulnerability was found in FlatPress. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,

CVE-2022-40047 MEDIUM POC
5.4 Oct 11

Flatpress v1.2.1 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the page parameter a

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy