Security readout for executives and security teams
Plain-English summary
CVE-2026-1935 affects the WordPress plugin Company Posts for LinkedIn up to version 1.0.0. A logged-in low-privilege user, such as a Subscriber, can delete LinkedIn post data stored by the plugin. This is not a site takeover issue, but it can disrupt LinkedIn content management and cause data loss inside WordPress.
Executive priority
Treat as a moderate-priority WordPress plugin issue. It does not indicate full compromise, but it can let any low-privilege logged-in user delete business content data. Prioritize sites with open registration, many Subscribers, or operational reliance on LinkedIn post synchronization.
Technical view
The plugin lacks an authorization capability check in linkedin_company_post_reset_handler(), hooked to admin_post_reset_linkedin_company_post. Authenticated users with Subscriber-level access or higher can trigger deletion of LinkedIn post data in the WordPress options table. CVSS is 4.3, vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, mapped to CWE-862.
Likely exposure
Exposure is limited to WordPress sites running Company Posts for LinkedIn version 1.0.0 or earlier and allowing untrusted or low-privilege authenticated accounts. Sites without the plugin, without authenticated public registration, or without low-trust users have lower practical exposure.
Exploitation context
The sources do not report active exploitation, and this CVE is not listed as KEV in the provided bundle. Exploitation requires a valid WordPress account with Subscriber-level access or higher. The impact described is deletion of stored LinkedIn post data, not code execution or credential theft.
Researcher notes
There is a minor source inconsistency: the affected metadata lists version "0" with defaultStatus unaffected, while the description and Wordfence-style summary state all versions up to and including 1.0.0 are vulnerable. Use the descriptive affected range unless vendor clarification says otherwise.
Mitigation direction
- Identify whether Company Posts for LinkedIn is installed and its version.
- If version 1.0.0 or earlier is present, review vendor guidance for an update or fix.
- Restrict or remove untrusted Subscriber-level accounts until remediation is confirmed.
- Back up WordPress options and plugin-related data before making changes.
- Consider disabling the plugin if business impact is acceptable and no fix is available.
Validation and detection
- Check the WordPress plugin inventory for Company Posts for LinkedIn.
- Confirm whether installed versions are 1.0.0 or earlier.
- Review user registration and Subscriber account exposure on affected sites.
- Verify whether plugin data backups include WordPress options table entries.
- Monitor administrative logs for unexpected reset actions related to LinkedIn company posts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1935 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/4c635405-997e-44ea-8851-7d09051307ad?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/company-posts-for-linkedin/trunk/admin/class-linkedin-company-posts-admin.php#L625CVE reference
- https://plugins.trac.wordpress.org/browser/company-posts-for-linkedin/tags/1.0.0/admin/class-linkedin-company-posts-admin.php#L625CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.