Cisco Small Business SPA500 Series IP Phones Local Command Execution Vulnerability
Noroxi assessment
Priority: Monitor (action score 26/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.47% (FIRST EPSS).
- Physical access to the device is required. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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
A vulnerability in Cisco Small Business SPA500 Series IP Phones could allow a physically proximate attacker to execute arbitrary commands on the device. The vulnerability is due to improper input validation in the device configuration interface. An attacker could exploit this vulnerability by accessing the configuration interface, which may require a password, and then accessing the device's physical interface and inserting a USB storage device. A successful exploit could allow the attacker to execute arbitrary commands on the device in an elevated security context. At the time of publication, this vulnerability affected Cisco Small Business SPA500 Series IP Phones firmware releases 7.6.2SR5 and prior.
- Published
- Jul 17, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- CWE-77
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.6
- CNA · cisco
- 6.6
- agree
CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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
- No fixed version yet
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 |
|---|---|---|
| cisco | spa501g firmware | cpe:2.3:o:cisco:spa501g_firmware |
| cisco | spa501g | cpe:2.3:h:cisco:spa501g |
| cisco | spa502g firmware | cpe:2.3:o:cisco:spa502g_firmware |
| cisco | spa502g | cpe:2.3:h:cisco:spa502g |
| cisco | spa504g firmware | cpe:2.3:o:cisco:spa504g_firmware |
| cisco | spa504g | cpe:2.3:h:cisco:spa504g |
| cisco | spa508g firmware | cpe:2.3:o:cisco:spa508g_firmware |
| cisco | spa508g | cpe:2.3:h:cisco:spa508g |
| cisco | spa509g firmware | cpe:2.3:o:cisco:spa509g_firmware |
| cisco | spa509g | cpe:2.3:h:cisco:spa509g |
| cisco | spa512g firmware | cpe:2.3:o:cisco:spa512g_firmware |
| cisco | spa512g | cpe:2.3:h:cisco:spa512g |
and 8 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cisco spa500ds firmwareup to 7.6.2sr5 inclusive
- cisco spa500s firmwareup to 7.6.2sr5 inclusive
- cisco spa501g firmwareup to 7.6.2sr5 inclusive
- cisco spa502g firmwareup to 7.6.2sr5 inclusive
- cisco spa504g firmwareup to 7.6.2sr5 inclusive
- cisco spa508g firmwareup to 7.6.2sr5 inclusive
- cisco spa509g firmwareup to 7.6.2sr5 inclusive
- cisco spa512g firmwareup to 7.6.2sr5 inclusive
- cisco spa514g firmwareup to 7.6.2sr5 inclusive
- cisco spa525g2 firmwareup to 7.6.2sr5 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (cisco). Independent of NVD's CPE analysis and usually ahead of it.
Cisco Cisco SPA525G2 5-line IP Phone
- unspecified and later · before 7.6.2SR5affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
No nightly-computed relations.
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
- Physical access to the device is required.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')CVSS vector
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
- LDAP InjectionCAPEC-136likelihood: High · High
- Command DelimitersCAPEC-15likelihood: High · High
- IMAP/SMTP Command InjectionCAPEC-183Medium
- Command InjectionCAPEC-248likelihood: Medium · High
- Manipulating Writeable Terminal DevicesCAPEC-40likelihood: High · Very High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Manipulating Writeable Configuration FilesCAPEC-75likelihood: High · Very High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.