How severe is CVE-2023-1069?

CVE-2023-1069 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-1069?

CVE-2023-1069 affects the following packages: really-simple-plugins/complianz-gdpr (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2023-1069?

Update really-simple-plugins/complianz-gdpr to 6.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-1069 is resolved across your whole dependency graph.

How do I detect CVE-2023-1069 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for really-simple-plugins/complianz-gdpr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-1069 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2023-1069 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-1069, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-1069?

CVE-2023-1069 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2023-1069 published, and has it been updated?

CVE-2023-1069 was published on March 27, 2023 and was last updated on February 22, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2023-1069 — complianz-gdpr

MEDIUMFix: Really-Simple-Plugins/complianz-gdpr@e6c2c38

CVE-2023-1069 is a medium-severity (CVSS 5.4) vulnerability in really-simple-plugins/complianz-gdpr. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for really-simple-plugins/complianz-gdpr — see the affected versions and patch details below.

Complianz WordPress plugin vulnerable to cross-site scripting

Published

Mar 27, 2023

Updated

Feb 22, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-1069.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘really-simple-plugins/complianz-gdpr

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The Complianz WordPress plugin before 6.4.2, Complianz Premium WordPress plugin before 6.4.2 do not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`really-simple-plugins/complianz-gdpr`	all versions	6.4.2`composer require really-simple-plugins/complianz-gdpr:^6.4.2`

Affected Products

1 product · 2 configurations

Application

complianzreally-simple-plugins

< 6.4.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Complianz WordPress plugin before 6.4.2, Complianz Premium WordPress…

wpscan.comNVDMar 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for really-simple-plugins/complianz-gdpr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update really-simple-plugins/complianz-gdpr to 6.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-1069 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

The Complianz Premium WordPress plugin before 6.4.2 did not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

O3 Security · Impact-Aware SCA

Is CVE-2023-1069 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Mar 27, 2023

First exploit

Mar 31, 2023

4 days after disclosure — rapid exploitation

Last updated

Feb 22, 2024

Identifiers

CVE-2023-1069

References

Advisorynvd.nist.gov · CVE 2023 1069 Webgithub.com · e6c2c386cadb78f8cdcded1b000cbd38bd9ff043 Webwpscan.com · caacc50c 822e 46e9 bc0b 681349fd0dda Webwww.github.com/Really-Simple-P

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 22, 2024