LiveActive security incident?Get immediate response
CVE Record

CVE-2022-4027: Simple:Press <= 6.8 - Unauthenticated Stored Cross-Site Scripting via Forum Replies

The Simple:Press plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'postitem' parameter manipulated during a forum response in versions up to, and including, 6.8 due to insufficient input sanitization and output escaping that makes injecting object and embed tags possible. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages when responding to forum threads that will execute whenever a user accesses an injected page.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-4027 lets unauthenticated visitors store malicious script content in Simple:Press forum replies. The script can run when other users view the affected thread, creating risk to WordPress site users and administrators who browse forum pages.

Executive priority

Treat as high priority for public WordPress forums. The business risk is stored script execution against visitors or administrators, but the bundle does not establish active exploitation.

Technical view

Simple:Press Forum for WordPress versions up to and including 6.8 has stored XSS through the postitem parameter during forum responses. The issue is insufficient input sanitization and output escaping, allowing object and embed tags to be injected into rendered pages.

Likely exposure

Exposure is most likely on WordPress sites running Simple:Press Forum 6.8 or earlier, especially forums that allow unauthenticated users to reply to threads.

Exploitation context

The provided sources describe unauthenticated stored XSS and a high CVSS score. They do not show CISA KEV listing or cited evidence of active exploitation in the wild.

Researcher notes

The affected path is forum reply handling through postitem. Validation should focus on sanitization and escaping behavior in rendered replies, without using offensive payloads against production systems.

Mitigation direction

  • Inventory WordPress sites using Simple:Press Forum and identify versions up to 6.8.
  • Check Simple:Press or WordPress plugin guidance for the fixed release before updating.
  • Prioritize updating affected sites once vendor-confirmed remediation is available.
  • Consider restricting unauthenticated forum replies until remediation is validated.
  • Review forum content for unexpected object, embed, or script-like markup.

Validation and detection

  • Confirm whether Simple:Press Forum is installed on each WordPress site.
  • Record the installed plugin version and compare it against the affected range.
  • Inspect forum reply rendering for unsafe embedded markup in existing content.
  • Verify patched deployments no longer render untrusted object or embed tags.
  • Review web application logs for suspicious unauthenticated forum reply activity.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-4027 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-4027Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
simplepressSimple:Press Forum0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.