CVE-2026-4143
CSRF Vulnerability in Neos Connector for Fakturama Plugin
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| neos | connector_for_fakturama | to 0.0.14 (inc) |
| neos_connector_for_fakturama | neos_connector_for_fakturama | to 0.0.14 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Neos Connector for Fakturama plugin for WordPress has a vulnerability known as Cross-Site Request Forgery (CSRF) in all versions up to and including 0.0.14.
This vulnerability exists because the plugin's function ncff_add_plugin_page(), which handles updating settings, does not validate a security token called a nonce.
As a result, an attacker who is not authenticated can trick a site administrator into performing an action, such as clicking a malicious link, which then causes the plugin settings to be modified without the administrator's intent.
How can this vulnerability impact me? :
This vulnerability allows an unauthenticated attacker to change the plugin settings by tricking an administrator into clicking a malicious link.
Such unauthorized changes could potentially disrupt the normal operation of the plugin or the website, leading to security or functionality issues.
However, the vulnerability does not allow the attacker to directly access or steal data, as it does not impact confidentiality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know