Social Media Auto Poster unauthorized deletion and viewing of Buffer sync logs
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Social Media Auto Poster – Schedule & Publish to Buffer plugin for WordPress, from wpzinc, has a missing authorization check that lets an attacker delete and view Buffer sync log entries for any post, including posts written by administrators. The attacker must be logged in with contributor-level access or higher, and can exploit the flaw remotely over the network without any action from another user.
Written by a model
Original description
The Social Media Auto Poster – Schedule & Publish to Buffer plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.2.9. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to delete Buffer sync log history for and disclose Buffer sync log contents of arbitrary posts, including those authored by administrators. The nonce used as the sole gate is not bound to any specific post ID, so a nonce harvested from the attacker's own draft editor screen is valid against any arbitrary post ID submitted in the request.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129095 (Social Media Auto Poster <= 6.2.9 - Missing Authorization to Authenticated (Contributor+) Arbitrary Log Deletion and Disclosure via 'post'…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129095 (entry last updated 2026-11-21):
Affected:
- wpzinc Social Media Auto Poster – Schedule & Publish to Buffer: through 6.2.9
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129095 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129095 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/46b032e8-d11b-42d0-9693-ad06d8aeba09?source=cve
- https://plugins.trac.wordpress.org/browser/wp-to-buffer/tags/6.2.9/lib/social/includes/class-ajax.php#L197
- https://plugins.trac.wordpress.org/browser/wp-to-buffer/tags/6.2.9/lib/social/includes/class-ajax.php#L174
- https://plugins.trac.wordpress.org/browser/wp-to-buffer/tags/6.2.9/lib/social/includes/class-log.php#L840
- https://plugins.trac.wordpress.org/browser/wp-to-buffer/tags/6.2.9/lib/social/includes/class-ajax.php#L194
- https://plugins.trac.wordpress.org/browser/wp-to-buffer/tags/6.2.9/lib/social/includes/class-admin.php#L448
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3813184%40wp-to-buffer&new=3813184%40wp-to-buffer
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129095
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129095"}.Affected versions
- wpzinc Social Media Auto Poster – Schedule & Publish to Bufferthrough 6.2.9
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.4/10CVSS 5.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 9
Questions about CVE-2026-129095
Is CVE-2026-129095 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-129095?
Social Media Auto Poster – Schedule & Publish to Buffer: through 6.2.9.
Source: cve.now feed data
Related
- CVE-2025-32267WordPress WP to Hootsuite plugin <= 1.5.8 - Cross Site Request Forgery (CSRF) vulnerability
- CVE-2026-134292SurrealDB 1.0.0 before 4.0.0 Function Capability Bypass via JavaScript Built-in Bridge
- CVE-2026-134679WeddingShare through 1.8.2 Missing Authorization via MediaViewer GalleryItem
- CVE-2026-134246SiYuan 3.6.0 before 3.6.2 and 3.7.3 before 3.8.10 Missing Authorization in getDOMText Exposes Cached OCR Text
- CVE-2026-134389Frappe ERPNext 6.18.0 before 15.124.0 Unauthorized Document Access via Payment Requests
- CVE-2026-134393Frappe ERPNext 10.1.41 before 15.122.0 Missing Authorization in Manufacturing BOM Replacement
No corrections so far. Something wrong on this page? Report an error.