Secufor Oauth
Approved changes feed: RSS · Atom
cpe:2.3:a:secufor:secufor_oauth:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Secufor (88d4380e-d140-5347-977d-76f12dc400ac) |
|---|---|
| Product | Secufor Oauth (6b722774-2380-5e1a-b560-87fcedec258d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-7617 |
vulnerable | 2026-07-29 01:09:05.052660 |
Secufor_OAuth <= 1.0.7 - Missing Authorization to Unauthenticated Account Logout via 'secuforoauth_unregister_action' AJAX Action
MEDIUM (5.3)
The Secufor_OAuth plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to disconnect the WordPress site from its linked Secufor account by clearing the plugin's stored login token and user login configuration.
Published: 2026-06-24T05:33:25.583Z
Updated: 2026-06-24T19:41:26.946Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.