dbcve.org
Post FormWordPress extension · Themekraft

CVE-2023-25981

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-25
Fix available
A fix is available. Upgrade to after 2.8.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in ThemeKraft Post Form plugin <= 2.8.1 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 confidence

A stored XSS vulnerability exists in the ThemeKraft Post Form plugin versions 2.8.1 and below, allowing authenticated users with contributor-level permissions or higher to inject malicious JavaScript into form submissions that execute when viewed by other users.

MitigationUpdate the ThemeKraft Post Form plugin to the latest patched version. If no patched version is available, sanitize all form input/output in the plugin code and validate user permissions strictly.

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 FormWordPress extension
Affected:<= 2.8.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, locate 'ThemeKraft Post Form' (or 'ThemeKraft Post Form - Custom Post Type Generator'), and read the version number from the plugin description. Alternatively, check the plugin's main PHP file header for 'Version:' tag.
    Affected if The installed version is 2.8.1 or lower.
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that ThemeKraft Post Form shows as 'Active' under the plugin status.
    Affected if The plugin is active and version 2.8.1 or lower.
  3. Check for contributor-level users
    In WordPress admin, go to Users and review the role assigned to each user. Look for users with 'Contributor', 'Author', 'Editor', or 'Administrator' roles.
    Affected if Any user with Contributor role or higher exists while the vulnerable plugin is active.
  4. Inspect form submission storage
    If the plugin creates custom post types or stores submissions in the wp_posts table, query the database for recent entries: SELECT ID, post_title, post_type, post_date FROM wp_posts WHERE post_type LIKE '%tkfp%' OR post_type LIKE '%postform%' ORDER BY post_date DESC LIMIT 20;
    Affected if Form submissions exist in the database and the plugin version is 2.8.1 or lower.
  5. Review form field handling
    Examine the plugin's form configuration in WordPress admin. Look for any custom form fields created by the plugin and check if HTML/script tags appear in submitted values by viewing the submissions in the admin panel.
    Affected if Form fields accept and display unsanitized input that could contain script tags.

You are affected if ThemeKraft Post Form plugin version 2.8.1 or lower is installed and active on your WordPress site, especially if you have users with Contributor-level access or higher who can submit forms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.8.1
Interim mitigation

Update the ThemeKraft Post Form plugin to the latest patched version. If no patched version is available, sanitize all form input/output in the plugin code and validate user permissions strictly.

Recommended fix Moderate confidence

2.8.2 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Dashboard > Updates or Plugins > Installed Plugins
  3. Locate the 'Post Form' plugin by ThemeKraft
  4. Update the plugin to the latest available version (minimum 2.8.2)
  5. After update, verify the version number in the plugins list
  6. Test form functionality to confirm the stored XSS vulnerability is patched
Caveat Minor version update; review form settings after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Post Form Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25981 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25981 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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