CVE-2022-1763: Due to missing checks the Static Page eXtended WordPress plugin through 2.1 is vulnerable to CSRF attacks whic

Q: How do I fix CVE-2022-1763?

static page extended: upgrade to newer than 2.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-1763 being exploited?

CVE-2022-1763 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1763 affect?

CVE-2022-1763 affects static page extended. Severity is medium (CVSS 5.4). Due to missing checks the Static Page eXtended WordPress plugin through 2.1 is vulnerable to CSRF attacks which allows changing the plugin settings, including required user levels for specific features. This could also lead to Stored Cross-

Q: How urgent is CVE-2022-1763?

Priority 30/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2022-1763 is a medium-severity flaw (CVSS 5.4) affecting static page extended. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Due to missing checks the Static Page eXtended WordPress plugin through 2.1 is vulnerable to CSRF attacks which allows changing the plugin settings, including required user levels for specific features. This could also lead to Stored Cross-Site Scripting due to the lack of escaping in some of the settings

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.3% (top 77%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-06-13
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: static page extended project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-13 13:15 UTCPublished CVE record published
2026-06-17 04:23 UTCUpdated Record last modified

static page extended project static page extended UPGRADE

Affected: <= 2.1

Fixed in: newer than 2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy static-page-extended || rpm -q static-page-extended || static-page-extended --version

2. UPGRADE to newer than 2.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade static-page-extended

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade static-page-extended

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1763?

static page extended: upgrade to newer than 2.1. Exact commands for each OS are on this page.

Is CVE-2022-1763 being exploited?

CVE-2022-1763 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1763 affect?

CVE-2022-1763 affects static page extended. Severity is medium (CVSS 5.4). Due to missing checks the Static Page eXtended WordPress plugin through 2.1 is vulnerable to CSRF attacks which allows changing the plugin settings, including required user levels for specific features. This could also lead to Stored Cross-

How urgent is CVE-2022-1763?

Priority 30/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs