ProfilepressWordPress extension · Properfraction
CVE-2022-47444
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in ProfilePress Membership Team Paid Membership Plugin, Ecommerce, Registration Form, Login Form, User Profile & Restrict Content – ProfilePress plugin <= 4.5.3 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the ProfilePress WordPress plugin versions 4.5.3 and below. Attackers can inject malicious JavaScript through crafted URL parameters that are reflected in the page output without proper sanitization or output encoding.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ProfilepressWordPress extension
<= 4.5.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify ProfilePress plugin is installedCheck for the plugin directory at wp-content/plugins/profilepress or profilepress-premium, or run: wp plugin list --name=profilepressAffected if ProfilePress plugin files exist in the WordPress plugins directory
-
Determine installed ProfilePress versionRead the plugin version from the main PHP file header (e.g., profilepress.php) in the plugin directory, or run: wp plugin get profilepress --format=jsonAffected if The installed version is 4.5.3 or lower (any version <= 4.5.3 is affected)
-
Identify the WordPress site URL structure used with ProfilePressCheck which ProfilePress shortcodes or pages are active on the site (e.g., login, registration, password reset pages) by reviewing used shortcodes in posts/pages or the ProfilePress settingsAffected if Any ProfilePress page or shortcode is accessible on the site (the vulnerable code executes when URL parameters are reflected)
-
Inspect URL parameters for potential reflected XSSReview access logs or use browser developer tools to examine URLs hitting ProfilePress pages. Look for query string parameters being reflected in page output without encoding (e.g., ?error=, ?message=, or custom parameters)Affected if URL parameters from ProfilePress pages are reflected in the HTML output without proper sanitization (confirms the vulnerability is exploitable)
A user is affected if the ProfilePress plugin version is 4.5.3 or lower and ProfilePress pages or shortcodes are publicly accessible, allowing attackers to inject malicious scripts via URL parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the ProfilePress plugin to a version newer than 4.5.3, which contains the fix for this reflected XSS vulnerability.
Fix this in Profilepress
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-47444 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data