CVE-2026-40776: WordPress Eventin plugin <= 4.1.8 - Broken Access Control vulnerability
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Arraytics WP Event SOlution 4.1.9.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Arraytics WP Event SOlution 4.1.9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Unauthenticated Broken Access Control in WP Event SOlution <= 4.1.8 versions.
- Published
- Jun 15, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-862
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Patchstack
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Is Eventin – Events Calendar, Tickets, Registration, Booking & WooCommerce on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Patchstack). Independent of NVD's CPE analysis and usually ahead of it.
Arraytics WP Event SOlution
- n/a and later · up to and including 4.1.8affectedfixed in 4.1.9
Same product
arraytics: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-68045WordPress WP Event SOlution plugin <= 4.1.12 - Broken Access Control vulnerability30Monitor
- CVE-2026-112844WordPress WP Event Solution plugin <= 4.1.26 - Cross Site Scripting (XSS) vulnerability28Monitor
- CVE-2026-28173WordPress WP Event SOlution plugin <= 4.1.19 - Arbitrary Content Deletion vulnerability28Monitor
Published before and after this one in the same product
- Later →CVE-2026-66451Aug 6, 2026 · WordPress WP Event SOlution plugin <= 4.1.9 - Broken Authentication vulnerability26Monitor
- Later →CVE-2026-28174Aug 13, 2026 · WordPress WP Event SOlution plugin <= 4.1.18 - Sensitive Data Exposure vulnerability26Monitor
- Later →CVE-2026-82223Sep 2, 2026 · WordPress WP Event SOlution plugin <= 4.1.22 - Broken Access Control vulnerability26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Arraytics WP Event SOlution | 4.1.9 | Vendor (CNA) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:2 | 2026-05-06 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-41 d
- Published
- TodayOct 30, 2026+137 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Lorenzo FradeaniPatchstack Bug Bounty Programfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-680451 days apartWordPress WP Event SOlution plugin <= 4.1.12 - Broken Access Control vulnerability30Monitor
- CVE-2026-2817359 days apartWordPress WP Event SOlution plugin <= 4.1.19 - Arbitrary Content Deletion vulnerability28Monitor
- CVE-2026-8222379 days apartWordPress WP Event SOlution plugin <= 4.1.22 - Broken Access Control vulnerability26Monitor
- CVE-2026-103684112 days apartWordPress WP Event Solution plugin <= 4.1.25 - Broken Access Control vulnerability21Monitor
- CVE-2026-109898120 days apartWordPress WP Event Solution plugin <= 4.1.25 - Broken Access Control vulnerability21Monitor
- CVE-2026-110380123 days apartWordPress WP Event Solution plugin <= 4.1.26 - Broken Access Control vulnerability21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0389 · Jun 16, 2026(WordPress Eklenti Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-862 · Missing AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.