Post Form Registration Form Profile Form For User Profiles And Content FormsWordPress extension · Themekraft
CVE-2022-38971
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 · uneditedStored Cross-Site Scripting (XSS) vulnerability in ThemeKraft Post Form – Registration Form – Profile Form for User Profiles and Content Forms for User Submissions plugin <= 2.7.5 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 · moderate confidenceStored XSS vulnerability in ThemeKraft Post Form plugin allows malicious JavaScript to be injected through user-submitted form fields (registration, profile, or content submission forms). The injected script is stored in the database and executes when other users view the affected content.
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
Post Form Registration Form Profile Form For User Profiles And Content FormsWordPress extension
<= 2.7.5CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 ThemeKraft Post Form plugin is installedCheck your WordPress plugins directory or WordPress admin panel under Plugins > Installed Plugins for 'ThemeKraft Post Form' or 'Post Form Registration Form Profile Form For User Profiles And Content Forms'Affected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for the version number next to the ThemeKraft Post Form plugin; alternatively, check the plugin's main PHP file for a version constant or the plugin header commentAffected if The version is 2.7.5 or lower
-
Identify active form typesCheck the plugin settings or shortcodes used on the site to determine if registration forms, profile forms, or content submission forms are active and publicly accessibleAffected if Any of these three form types (registration, profile, or content submission) are enabled and accessible to users
-
Inspect database for suspicious form submissionsQuery the WordPress database tables where the plugin stores form submissions (typically wp_postmeta, wp_usermeta, or custom tables created by the plugin) for patterns like <script, javascript:, onerror=, onload=, or other HTML/script tags in user-submitted fieldsAffected if Entries containing script tags or JavaScript event handlers are found in form submission data
-
Review page source for injected scriptsNavigate to pages where user-submitted content from forms is displayed, view the page source (right-click > View Page Source), and search for unexpected script tags or inline event handlers that originate from user input fieldsAffected if Unexpected script tags or JavaScript event handlers appear in rendered content that came from user form submissions
You are affected if the ThemeKraft Post Form plugin version is 2.7.5 or lower and any registration, profile, or content submission forms created by the plugin are active on your site, with potential malicious scripts stored in form submission data.
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 ThemeKraft Post Form plugin to a version newer than 2.7.5; alternatively, implement proper input sanitization and output encoding on all user-supplied form fields.
Fix this in Post Form Registration Form Profile Form For User Profiles And Content Forms
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38971 — 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-38971 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