51l3nc3, a member of the AXIS OS Bug Bounty Program, has found that the VAPIX API uploadoverlayimage.cgi did not have sufficient input valid
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Axis Communications AB AXIS OS 10.12.276, 11.11.141, 12.3.56.
Low priority for now. Upgrade to Axis Communications AB AXIS OS 10.12.276, 11.11.141, 12.3.56 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
51l3nc3, a member of the AXIS OS Bug Bounty Program, has found that the VAPIX API uploadoverlayimage.cgi did not have sufficient input validation to allow an attacker to upload files to block access to create image overlays in the web interface of the Axis device.
- Published
- Apr 8, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 30th percentile
- CWE
- CWE-1287
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.3
- CNA · Axis
- 4.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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.
| Vendor | Product | CPE |
|---|---|---|
| axis | axis os | cpe:2.3:o:axis:axis_os |
| axis | axis os 2022 | cpe:2.3:o:axis:axis_os_2022 |
| axis | axis os 2024 | cpe:2.3:o:axis:axis_os_2024 |
Using axis os? Add it to your stack and be the first to know about CVEs like this one. (IP camera)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- axis axis os10.12.0 and later · before 12.3.56
- axis axis os 2022before 10.12.276
- axis axis os 2024before 11.11.141
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Axis). Independent of NVD's CPE analysis and usually ahead of it.
Axis Communications AB AXIS OS
- 10.12.0 and later · before 10.12.276affected · semver
- 11.0.0 and later · before 11.11.141affected · semver
- 12.0.0 and later · before 12.3.56affected · semver
Same product
axis: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-1185A configuration file on the local file system had improper input validation which could allow code execution and potentially lead to privile35Monitor
- CVE-2025-11142The VAPIX API mediaclip.cgi that did not have a sufficient input validation allowing for a possible remote code execution.35Monitor
- CVE-2025-0358During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the VAPIX Device Configuration fra35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-0359Mar 4, 2025 · During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the ACAP Application framework tha22Monitor
- ← EarlierCVE-2025-0360Mar 4, 2025 · During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the VAPIX Device Configuration fra31Monitor
- Later →CVE-2025-0361Apr 8, 2025 · During an annual penetration test conducted on behalf of Axis Communications, Truesec discovered a flaw in the VAPIX Device Configuration fr21Monitor
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 |
|---|---|---|
| Axis Communications AB AXIS OS | 10.12.276 | Vendor (CNA) |
| Axis Communications AB AXIS OS | 11.11.141 | Vendor (CNA) |
| Axis Communications AB AXIS OS | 12.3.56 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-0802399 days apartAn ACAP configuration file lacked sufficient input validation, which could allow command injection and potentially lead to privilege escalat29Monitor
- CVE-2025-30027126 days apartAn ACAP configuration file lacked sufficient input validation, which could allow for arbitrary code execution.26Monitor
- CVE-2025-4645217 days apartAn ACAP configuration file lacked sufficient input validation, which could allow for arbitrary code execution.26Monitor
- CVE-2025-6298217 days apartACAP applications can gain elevated privileges due to improper input validation, potentially leading to privilege escalation.26Monitor
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).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-1287 · Improper Validation of Specified Type of InputCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.