Wolf Wordpress Posts Bulk Editor And Products Manager ProfessionalWordPress extension · Pluginus
CVE-2023-31218
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 · uneditedCross-Site Request Forgery (CSRF) leading to Stored Cross-Site Scripting (XSS) vulnerability in realmag777 WOLF – WordPress Posts Bulk Editor and Manager Professional plugin <= 1.0.6 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 confidenceA CSRF vulnerability in the WOLF WordPress Posts Bulk Editor and Manager Professional plugin (versions <=1.0.6) allows unauthenticated attackers to trick authenticated administrators into submitting crafted requests that inject malicious JavaScript, which gets stored (XSS) in the WordPress database. The lack of CSRF token validation on plugin actions enables the attack.
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
Wolf Wordpress Posts Bulk Editor And Products Manager ProfessionalWordPress extension
< 1.0.7CVSS 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.
-
Check the installed WOLF plugin versionNavigate to WordPress dashboard > Plugins > Installed Plugins. Find 'WOLF | Wordpress Posts Bulk Editor And Products Manager Professional' and look at the version number displayed under the plugin name.Affected if The installed version is 1.0.6 or lower (any version below 1.0.7).
-
Confirm the plugin is activeIn the Plugins page, verify that the WOLF plugin has an 'Active' status underneath its name.Affected if The plugin is both installed at a vulnerable version AND active. An inactive plugin cannot be exploited.
-
Inspect recent posts for injected scriptsGo to Posts > All Posts in the WordPress admin. Review recent post titles and content for any unexpected script tags, iframe tags, or encoded JavaScript (such as <script>, <img src=x onerror=>, javascript:, or base64-encoded payloads). Use the browser's Inspect tool if needed.Affected if Any post contains suspicious JavaScript that was not intentionally added by your editorial team.
-
Check post meta and bulk edit historyIf the WOLF plugin has a bulk edit or history feature, review recent bulk actions in the plugin's logs or the wp_posts table in the database for any unexpected content modifications involving script tags.Affected if Recent bulk edits or post modifications contain malicious script injections.
You are affected if the WOLF plugin is active at version 1.0.6 or lower, or if you find injected JavaScript in any WordPress posts that correlates with the time this vulnerable plugin was in use.
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.
dbcve · scoped1.0.7
Update the WOLF plugin to version 1.0.7 or later. If no patch is available, disable the plugin. Audit the site for any injected scripts in post content and review admin user sessions for compromise.
1.0.7
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'WOLF – WordPress Posts Bulk Editor and Manager Professional'
- If the current version is below 1.0.7, click 'Update Now' to upgrade to version 1.0.7
- Verify the update completed successfully and the plugin is now at version 1.0.7
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wolf Wordpress Posts Bulk Editor And Products Manager Professional
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31218 — 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-2023-31218 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